From: Josh Durgin <josh.durgin@inktank.com>
To: Felix Feinhals <ff@turtle-entertainment.de>
Cc: ceph-devel@vger.kernel.org
Subject: Re: MDS crash, wont startup again
Date: Thu, 17 May 2012 14:38:25 -0700 [thread overview]
Message-ID: <4FB56FD1.5090805@inktank.com> (raw)
In-Reply-To: <CA+WUqKyFusqxiPkPvQeSaP_nPBd5_ab4nLz1xWeOZZqMLk1SBA@mail.gmail.com>
On 05/16/2012 01:11 AM, Felix Feinhals wrote:
> Hi again,
>
> anything on this Problem? Seems that the only choice for me is to
> reinitialize the whole cephfs (mkcephfs...)
> :(
Hi Felix, it looks like your first mail never reached the list.
> 2012/5/10 Felix Feinhals<ff@turtle-entertainment.de>:
>> Hi List,
>>
>> we installed a ceph cluster with ceph version 0.46.
>> 3 OSDs, 3 MONs and 3 MDSs.
>>
>> After copying a bunch of files to a ceph-fuse mount all MDS daemons
>> crash and now i cant bring them back online.
>> I already tried to restart the daemons in different order and also
>> removed one OSD, nothing really happened only now we have pgs with
>> active+remapped which i think is normal.
>> Any hints?
Are all three MDS active? At this point, more than one active MDS is
likely to crash. You can have one active and others standby.
If you've got only one active, what was the backtrace of the crash?
It'll be at the end of the MDS log (by default in /var/log/ceph).
next prev parent reply other threads:[~2012-05-17 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+WUqKxZoh_5k5qgtUFwnsr2=gaZ4_RONazYQG7enKa75WhNVQ@mail.gmail.com>
2012-05-16 8:11 ` MDS crash, wont startup again Felix Feinhals
2012-05-17 21:38 ` Josh Durgin [this message]
2012-05-21 12:38 ` Felix Feinhals
2012-05-21 18:44 ` Gregory Farnum
2012-05-22 10:12 ` Felix Feinhals
2012-05-22 17:56 ` Greg Farnum
2012-05-23 12:28 ` Felix Feinhals
2012-05-23 21:39 ` Gregory Farnum
2012-05-24 12:29 ` Felix Feinhals
2012-06-04 19:49 ` Greg Farnum
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=4FB56FD1.5090805@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ff@turtle-entertainment.de \
/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.