From: "Matt W. Benjamin" <matt@linuxbox.com>
To: David Zafman <david.zafman@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: wip-libcephfs-emp-rb
Date: Mon, 7 Oct 2013 19:48:29 -0400 (EDT) [thread overview]
Message-ID: <567038737.154.1381189709014.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <0E0D6667-6E38-420E-8FF7-751350482313@inktank.com>
Hi David,
I'll have a loot.
Matt
----- "David Zafman" <david.zafman@inktank.com> wrote:
> I rebased wip-libcephfs and pushed as wip-libcephfs-emp-rb so that we
> can get this in to the Emperor release. Sage mentioned that he had hit
> a fuse problem in the wip-libcephfs branch, so apparently the problem
> is still present. Have you run into this bug in your testing? Are you
> testing with these modification to Ceph?
>
>
>
> 2013-10-04T10:39:01.664
> INFO:teuthology.task.workunit.client.0.out:[10.214.132.22]: CC
> kernel/softirq.o
> 2013-10-04T10:39:02.059
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]: ***
> Caught signal (Segmentation fault) **
> 2013-10-04T10:39:02.059
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]: in
> thread 7f57fa316780
> 2013-10-04T10:39:02.073
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]: ceph
> version 0.69-500-g09f4df0 (09f4df02a866230b19539b03061f4abc5ab47ae2)
> 2013-10-04T10:39:02.073
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]: 1:
> ceph-fuse() [0x5e0d1a]
> 2013-10-04T10:39:02.073
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]: 2:
> (()+0xfcb0) [0x7f57f9cc5cb0]
> 2013-10-04T10:39:02.073
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]: 3:
> (Client::_get_inodeno(Inode*)+0) [0x52dd10]
> 2013-10-04T10:39:02.073
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]: 4:
> (Client::ll_forget(Inode*, int)+0x4a) [0x538d1a]
> 2013-10-04T10:39:02.074
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]: 5:
> ceph-fuse() [0x52a1c5]
> 2013-10-04T10:39:02.074
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]: 6:
> (fuse_session_loop()+0x75) [0x7f57f9ee3d65]
> 2013-10-04T10:39:02.074
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]: 7:
> (main()+0x84c) [0x5266fc]
> 2013-10-04T10:39:02.074
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]: 8:
> (__libc_start_main()+0xed) [0x7f57f83f576d]
> 2013-10-04T10:39:02.074
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]: 9:
> ceph-fuse() [0x527c99]
> 2013-10-04T10:39:02.074
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]:
> 2013-10-04 10:39:02.072487 7f57fa316780 -1 *** Caught signal
> (Segmentation fault) **
> 2013-10-04T10:39:02.074
> INFO:teuthology.task.ceph-fuse.ceph-fuse.0.err:[10.214.132.22]: in
> thread 7f57fa316780
>
>
>
> David Zafman
> Senior Developer
> http://www.inktank.com
--
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI 48104
http://linuxbox.com
tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309
next parent reply other threads:[~2013-10-07 23:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0E0D6667-6E38-420E-8FF7-751350482313@inktank.com>
2013-10-07 23:48 ` Matt W. Benjamin [this message]
2013-10-07 23:08 wip-libcephfs-emp-rb David Zafman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=567038737.154.1381189709014.JavaMail.root@thunderbeast.private.linuxbox.com \
--to=matt@linuxbox.com \
--cc=ceph-devel@vger.kernel.org \
--cc=david.zafman@inktank.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.