From: Thomas Mueller <thomas@chaschperli.ch>
To: ceph-devel@vger.kernel.org
Subject: cmds segfault on pdj-fstest (ceph.git unstable)
Date: Wed, 9 Jun 2010 06:48:58 +0000 (UTC) [thread overview]
Message-ID: <hundgq$ums$1@dough.gmane.org> (raw)
hi
since this morning cmds segfaults on the pdj-fstest.
(git rev 12798de37169f6561f0dc7643ca626957f7ab37e)
What happend:
<start server with vstart.sh>
<mount>
08:39:08 [ 176.460708] ceph: loaded (mon/mds/osd proto 15/32/24, osdmap 5/5 5/5)
08:39:08 [ 176.463965] ceph: client4101 fsid a7b6294d-a074-8e0e-2cee-a48fe2f85c86
08:39:08 [ 176.464240] ceph: mon1 127.0.0.1:6789 session established
<start pdj-fstest>
08:40:51 [ 279.406980] cmds[6675]: segfault at 0 ip 00000000004bddbd sp 00007f6861ba34e0 error 4 in cmds[400000+331000]
08:40:51 [ 279.409895] ceph: mds0 127.0.0.1:6802 socket closed
08:40:51 [ 279.804386] ceph: mds0 127.0.0.1:6802 connection failed
08:40:52 [ 280.804383] ceph: mds0 127.0.0.1:6802 connection failed
08:40:54 [ 282.804381] ceph: mds0 127.0.0.1:6802 connection failed
08:40:58 [ 286.804387] ceph: mds0 127.0.0.1:6802 connection failed
08:41:06 [ 294.804793] ceph: mds0 127.0.0.1:6802 connection failed
<killed pdj-fstest>
08:41:22 [ 310.804820] ceph: mds0 127.0.0.1:6802 connection failed
08:41:38 [ 326.804288] ceph: mds0 caps stale
08:41:53 [ 341.804327] ceph: mds0 caps stale
08:41:54 [ 342.804245] ceph: mds0 127.0.0.1:6802 connection failed
the segfault is reproducable on my machine. yesterday
(git rev 58fe4b8d5441982d0103817666a6d1bfdd8e04cd) this error was not present.
- Thomas
next reply other threads:[~2010-06-09 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 6:48 Thomas Mueller [this message]
2010-06-10 9:51 ` cmds segfault on pdj-fstest (ceph.git unstable) Thomas Mueller
2010-06-10 11:38 ` Henry C Chang
2010-06-10 16:11 ` Gregory Farnum
2010-06-10 16:26 ` Gregory Farnum
2010-06-11 2:17 ` Henry C Chang
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='hundgq$ums$1@dough.gmane.org' \
--to=thomas@chaschperli.ch \
--cc=ceph-devel@vger.kernel.org \
/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.