From: Phil Turmel <philip@turmel.org>
To: Keith Phillips <spootsy.ootsy@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Fwd: Help with failed RAID-5 -> 6 migration
Date: Thu, 13 Jun 2013 10:09:17 -0400 [thread overview]
Message-ID: <51B9D28D.8040702@turmel.org> (raw)
In-Reply-To: <CAASLJ=7=hnez3udgc4Voa_i7drZq_Y-8FkOgxt02_ROL5eD3qg@mail.gmail.com>
On 06/13/2013 09:58 AM, Keith Phillips wrote:
>> You won't be able to assemble and run your array without a backup file.
>> You said you lost your original, so you will have to use a blank one
>> and tell mdadm to ignore the invalid file.
>
> Ah, didn't realise this was an option. After a brief googling it seems
> my version of mdadm pre-dated the "--invalid-backup" option.
>
> Cloned the git repo and built a newer version, and re-assembled with
> an empty "--backup-file" and the "--invalid-backup" option. Now it's
> chugging along happily again - at %20 and counting now, no errors in
> sight!
Good to hear. :-)
> Will do an ext4 fsck once it's finished the grow. Are there any tips
> for determining what data I trashed by losing the backup-file? Or is
> it just a case of trying to access stuff and seeing what's broken?
You have the reshape position where the process stopped in the original
mdadm -E reports. Use that to query for inodes that contain those
sectors, then look up those inodes.
A quick google came up with:
http://smartmontools.sourceforge.net/badblockhowto.html
You'll have to reinterpret that to use the sector offsets in your array
rather than sector offset from smartctl.
> Thanks so much for the help, Phil :)
You're welcome.
Phil
prev parent reply other threads:[~2013-06-13 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 3:02 Help with failed RAID-5 -> 6 migration Keith Phillips
2013-06-08 22:43 ` Phil Turmel
2013-06-08 23:02 ` Phil Turmel
[not found] ` <CAASLJ=5JkQ8L9fbrOSUKH8Y-a7PZgkTcCsi6PW=rhzsUPRF6ow@mail.gmail.com>
2013-06-10 16:16 ` Fwd: " Keith Phillips
2013-06-10 19:35 ` Phil Turmel
2013-06-11 2:08 ` Keith Phillips
2013-06-11 10:44 ` Phil Turmel
2013-06-11 12:42 ` Vanhorn, Mike
[not found] ` <CAASLJ=6eEVY6DeZ=+9Aw6yXmqNSc5mygqtD_8y+MaUid6B_TcQ@mail.gmail.com>
2013-06-12 14:51 ` Fwd: " Phil Turmel
[not found] ` <51B88AB2.5060303@turmel.org>
[not found] ` <CAASLJ=7=hnez3udgc4Voa_i7drZq_Y-8FkOgxt02_ROL5eD3qg@mail.gmail.com>
2013-06-13 14:09 ` Phil Turmel [this message]
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=51B9D28D.8040702@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=spootsy.ootsy@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 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.