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 15:53:14 +0100 [thread overview]
Message-ID: <50EC32DA.40307@ledeuns.net> (raw)
In-Reply-To: <AEBA0243790A484AA72D5CDF477159BC1CEB016A@SN2PRD0106MB178.prod.exchangelabs.com>
Le 08/01/2013 14:51, Moore, Shawn M a écrit :
> If you know the prefix (which is seems you do) and the original size of the rbd you should be able to use my utility.
>
> https://github.com/smmoore/ceph/blob/master/rbd_restore.sh
>
> You will need all the rados files in the current working directory you execute the script from. We have used it many times so far and works for us. I have not had any outside feedback on it's usage. But if you are truly missing any files, it will seek over them and your rbd might be corrupt. Likewise if a file itself is damaged, it will write what is in that file to the rebuild.
>
Thank you very much Shawn, that's your script that gave me the idea of
rebuiding the RBD from files ;-)
I coded my own script which find the RBD files itself.
Denis
--
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:[~2013-01-08 14:53 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
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 [this message]
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=50EC32DA.40307@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.