From: Thomas Mueller <thomas@chaschperli.ch>
To: Gregory Farnum <gregf@hq.newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: mds crash on snaptest-2
Date: Tue, 27 Jul 2010 21:50:14 +0200 [thread overview]
Message-ID: <4C4F3876.3030306@chaschperli.ch> (raw)
In-Reply-To: <AANLkTimrW=DquX_Pyi8M7wb_GWV1DJr6w28LTOC9RkfD@mail.gmail.com>
>> the test still fails with ceph.git/unstable from today. now cmds doesn't
>> exit anymore. But after a half an hour the test kills itself because of a
>> timeout (normal running time is about 10 minutes).
>>
>> - Thomas
>>
>> PS: found out that vstart.sh places logs in subdir "out" too. so tell me
>> if you need some of them.
> Yes, I've been working on this for some time now. If you try the test
> on a single MDS it should work fine with the latest git, but there are
> some deeper issues going on with an MDS cluster that we're having a
> hard time isolating in a way that lets us fix it. It appears we might
> need to rework our snapshot inode handling a bit and Sage has asked me
> to move on.
>
> I'd recommend doing your testing on a single MDS (if using vstart:
> CEPH_NUM_MDS=1 ./vstart -- this also works for _OSD and _MON) system
> until we say that we expect the MDS cluster to work under more
> circumstances.
i'm always starting just one daemon. my test script sets these vars
before calling "vstart.sh":
export CEPH_NUM_MON=1
export CEPH_NUM_OSD=1
export CEPH_NUM_MDS=1
last known good rev was ae82dd5a5c964bb310a5512d10d1e062cbb0c1a5 on
July 8 - with this rev the test was working fine.
i've also tried to compile with "-O0" to run it with gdb (not that i'm a
gdb expert..) - but the binaries failed to start (ok back then it was
bit late ...)
- Thomas
next prev parent reply other threads:[~2010-07-27 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 14:57 mds crash on snaptest-2 Thomas Mueller
2010-07-19 21:16 ` Gregory Farnum
2010-07-20 14:50 ` Thomas Mueller
2010-07-27 9:22 ` Thomas Mueller
2010-07-27 18:59 ` Gregory Farnum
2010-07-27 19:50 ` Thomas Mueller [this message]
2010-07-27 19:54 ` Gregory Farnum
2010-07-28 5:03 ` Thomas Mueller
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=4C4F3876.3030306@chaschperli.ch \
--to=thomas@chaschperli.ch \
--cc=ceph-devel@vger.kernel.org \
--cc=gregf@hq.newdream.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox