From: Denis Fondras <ceph@ledeuns.net>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Is Ceph recovery able to handle massive crash
Date: Tue, 08 Jan 2013 09:44:14 +0100 [thread overview]
Message-ID: <50EBDC5E.3090207@ledeuns.net> (raw)
In-Reply-To: <E4EA8440A5CF4E519F57FE3D9C26CAE4@inktank.com>
Hello,
I tried to upgrade to 0.56.1 this morning as it could help with
recovery. No luck so far...
> What's wrong with your primary OSD?
I don't know what's really wrong. The disk seems fine.
> In general they shouldn't really be crashing that frequently and if you've got a new bug we'd like to diagnose and fix it.
I don't know if it is hardware related (it seems not as I tested each
parts). Then it might be an issue with btrfs (linux 3.5) or Ceph or
another software part.
However, I'm willing to resolve this issue. Just tell me what you need,
what I can do.
> If that can't be done (or it's a hardware failure or something), you can mark the OSD lost, but that might lose data and then you will be sad.
Well, if I must have a loss I'd really like to try everything before :)
Denis
next prev parent reply other threads:[~2013-01-08 8:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 12:19 Is Ceph recovery able to handle massive crash Denis Fondras
2013-01-05 15:24 ` Gregory Farnum
2013-01-07 17:25 ` Denis Fondras
2013-01-07 21:30 ` Gregory Farnum
2013-01-08 8:44 ` Denis Fondras [this message]
2013-01-08 12:57 ` Denis Fondras
2013-01-08 13:10 ` Wido den Hollander
2013-01-08 13:36 ` Wido den Hollander
2013-01-08 13:51 ` Moore, Shawn M
2013-01-08 14:53 ` Denis Fondras
2013-01-08 17:09 ` Gregory Farnum
2013-01-08 19:44 ` Denis Fondras
2013-01-08 23:36 ` Gregory Farnum
2013-01-09 8:30 ` Denis Fondras
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=50EBDC5E.3090207@ledeuns.net \
--to=ceph@ledeuns.net \
--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.