From: Yann Dupont <Yann.Dupont@univ-nantes.fr>
To: Tommi Virtanen <tv@inktank.com>
Cc: Sam Just <sam.just@inktank.com>, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: domino-style OSD crash
Date: Mon, 09 Jul 2012 21:05:04 +0200 [thread overview]
Message-ID: <4FFB2B60.5000201@univ-nantes.fr> (raw)
In-Reply-To: <CADvuQRFQCrQn3dF=r6VLPo3Q5vBVvCROowa99Rfak=qkbXb0rA@mail.gmail.com>
Le 09/07/2012 19:43, Tommi Virtanen a écrit :
> On Wed, Jul 4, 2012 at 1:06 AM, Yann Dupont <Yann.Dupont@univ-nantes.fr> wrote:
>> Well, I probably wasn't clear enough. I talked about crashed FS, but i was
>> talking about ceph. The underlying FS (btrfs in that case) of 1 node (and
>> only one) has PROBABLY crashed in the past, causing corruption in ceph data
>> on this node, and then the subsequent crash of other nodes.
>>
>> RIGHT now btrfs on this node is OK. I can access the filesystem without
>> errors.
> But the LevelDB isn't. It's contents got corrupted, somehow somewhere,
> and it really is up to the LevelDB library to tolerate those errors;
> we have a simple get/put interface we use, and LevelDB is triggering
> an internal error.
Yes, understood.
>> One node had problem with btrfs, leading first to kernel problem , probably
>> corruption (in disk/ in memory maybe ?) ,and ultimately to a kernel oops.
>> Before that ultimate kernel oops, bad data has been transmitted to other
>> (sane) nodes, leading to ceph-osd crash on thoses nodes.
> The LevelDB binary contents are not transferred over to other nodes;
Ok thanks for the clarification ;
> this kind of corruption would not spread over the Ceph clustering
> mechanisms. It's more likely that you have 4 independently corrupted
> LevelDBs. Something in the workload Ceph runs makes that corruption
> quite likely.
Very likely : since I reformatted my nodes with XFS I don't have
problems so far.
>
> The information here isn't enough to say whether the cause of the
> corruption is btrfs or LevelDB, but the recovery needs to handled by
> LevelDB -- and upstream is working on making it more robust:
> http://code.google.com/p/leveldb/issues/detail?id=97
Yes, saw this. It's very important. Sometimes, s... happens. In respect
to the size ceph volumes can reach, having a tool to restart damaged
nodes (for whatever reason) is a must.
Thanks for the time you took to answer. It's much clearer for me now.
Cheers,
--
Yann Dupont - Service IRTS, DSI Université de Nantes
Tel : 02.53.48.49.20 - Mail/Jabber : Yann.Dupont@univ-nantes.fr
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-07-09 19:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 8:44 domino-style OSD crash Yann Dupont
2012-06-04 16:16 ` Tommi Virtanen
2012-06-04 17:40 ` Sam Just
2012-06-04 18:34 ` Greg Farnum
2012-07-03 8:40 ` Yann Dupont
2012-07-03 19:42 ` Tommi Virtanen
2012-07-03 20:54 ` Yann Dupont
2012-07-03 21:38 ` Tommi Virtanen
2012-07-04 8:06 ` Yann Dupont
2012-07-04 16:21 ` Gregory Farnum
2012-07-04 17:53 ` Yann Dupont
2012-07-05 21:32 ` Gregory Farnum
2012-07-06 7:19 ` Yann Dupont
2012-07-06 17:01 ` Gregory Farnum
2012-07-07 8:19 ` Yann Dupont
2012-07-09 17:14 ` Samuel Just
2012-07-10 9:46 ` Yann Dupont
2012-07-10 15:56 ` Tommi Virtanen
2012-07-10 16:39 ` Yann Dupont
2012-07-10 17:11 ` Tommi Virtanen
2012-07-10 17:36 ` Yann Dupont
2012-07-10 18:16 ` Tommi Virtanen
2012-07-09 17:43 ` Tommi Virtanen
2012-07-09 19:05 ` Yann Dupont [this message]
2012-07-09 19:48 ` Tommi Virtanen
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=4FFB2B60.5000201@univ-nantes.fr \
--to=yann.dupont@univ-nantes.fr \
--cc=ceph-devel@vger.kernel.org \
--cc=sam.just@inktank.com \
--cc=tv@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.