From: NeilBrown <neilb@suse.de>
To: Shaya Potter <spotter@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: recovering from raid5 corruption
Date: Mon, 30 Apr 2012 09:45:46 +1000 [thread overview]
Message-ID: <20120430094546.4702be0a@notabene.brown> (raw)
In-Reply-To: <4F9DCEC6.1050109@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2782 bytes --]
On Sun, 29 Apr 2012 19:29:10 -0400 Shaya Potter <spotter@gmail.com> wrote:
> On 04/29/2012 06:52 PM, NeilBrown wrote:
> >
> > You've written a new superblock 4K in to each device, where previously here
> > was something. So you have probably corrupted something though we cannot
> > easily tell what.
> >
> > Retry your experiment with --metadata=0.90. Hopefully one of those
> > combinations will work better. If it does, make a backup of the data you
> > want to keep, then I would suggest rebuilding the array from scratch.
>
> ok, thanks, that was a huge help.
>
> I have it setup correctly now (obvious due to the fact that I can read
> the lvm configuration without any gibberish when ordered correctly).
I should add that this only proves that you have the first device correct,
the rest may be wrong.
You need to activate the LVM, then look at the filesystem and see if it is
consistent before you can be sure that all devices are in the correct
position.
NeilBrown
>
> however, now I need to figure out how to recreate the lvm appropriately.
> I see the configuration "file" in at the start of the raid array (less
> -f /dev/md0 which I'm including below)
>
> I asusme there should be a way to reuse this data to recreate the lvm?
>
> any continued advice would be appreciated, googling doesn't seem to come
> up with much if one doesn't have a backup of the lvm data.
>
> raid5 {
> id = "8r27WQ-HvIw-0RQV-aksr-LJGN-DLVD-1WBg8h"
> seqno = 6
> status = ["RESIZEABLE", "READ", "WRITE"]
> extent_size = 8192
> max_lv = 0
> max_pv = 0
>
> physical_volumes {
>
> pv0 {
> id = "7P0W3p-XoPg-rCo8-HJ2G-Hfxc-UDWI-x6nQck"
> device = "/dev/md0"
>
> status = ["ALLOCATABLE"]
> dev_size = 11721107456
> pe_start = 384
> pe_count = 1430799
> }
> }
>
> logical_volumes {
>
> data {
> id = "YZvrHt-Glyr-wnj0-QzV1-qRe6-VcRH-D7wU3U"
> status = ["READ", "WRITE", "VISIBLE"]
> segment_count = 1
>
> segment1 {
> start_extent = 0
> extent_count = 524288
>
> type = "striped"
> stripe_count = 1 # linear
>
> stripes = [
> "pv0", 0
> ]
> }
> }
>
> image {
> id = "uHOzpc-l8L7-eF5h-Fa0C-EsCS-sM6X-3GpOP0"
> status = ["READ", "WRITE", "VISIBLE"]
> segment_count = 1
>
> segment1 {
> start_extent = 0
> extent_count = 906511
>
> type = "striped"
> stripe_count = 1 # linear
> stripes = [
> "pv0", 524288
> ]
> }
> }
> }
> }
> # Generated by LVM2 version 2.02.39 (2008-06-27): Wed Aug 19 23:36:50 2009
>
> contents = "Text Format Volume Group"
> version = 1
>
> description = ""
>
> creation_host = "nas" # Linux nas 2.6.27-14-generic #1 SMP Fri Jul 24
> 22:19:33 UTC 2009 i686
> creation_time = 1250739410 # Wed Aug 19 23:36:50 2009
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-04-29 23:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 22:38 recovering from raid5 corruption Shaya Potter
2012-04-29 22:52 ` NeilBrown
2012-04-29 23:29 ` Shaya Potter
2012-04-29 23:41 ` Shaya Potter
2012-04-29 23:44 ` NeilBrown
2012-04-29 23:45 ` NeilBrown [this message]
2012-04-29 23:51 ` Shaya Potter
2012-04-30 0:46 ` Shaya Potter
2012-04-30 1:09 ` NeilBrown
2012-04-30 1:13 ` Shaya Potter
2012-04-30 6:29 ` Jan Ceuleers
2012-04-30 15:33 ` Shaya Potter
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=20120430094546.4702be0a@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=spotter@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).