From: NeilBrown <neilb@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-raid@vger.kernel.org, marcin.labun@intel.com,
ed.ciechanowski@intel.com
Subject: Re: [PATCH 0/9] recovering an imsm raid5 array
Date: Tue, 30 Aug 2011 13:13:31 +1000 [thread overview]
Message-ID: <20110830131331.02adf4c2@notabene.brown> (raw)
In-Reply-To: <20110826020908.28015.52384.stgit@localhost6.localdomain6>
On Thu, 25 Aug 2011 19:13:59 -0700 Dan Williams <dan.j.williams@intel.com>
wrote:
> I run imsm raid5 and raid1 arrays on my personal systems and was
> recently bit by the bug that was fixed in commit 1a2487c2 "FIX: imsm:
> OROM does not recognize degraded arrays (V2)". In the process of
> investigating that I pulled the wrong disk and ended up in a dual
> degraded situation.
>
> These patches (ordered in roughly increasing order of required review)
> are the features needed to get the array up and running again, as well
> as some random fixes spotted along the way.
>
> The most important patch for recovery being patch7 "imsm: support
> 'missing' devices at Create", allowing the mdadm raid5 recovery path of
> recreating the raid array with what one thinks are the good disks /
> order, and then attempt to mount the filesystem to see if the guess was
> correct.
>
> Example, create degraded raid5 with slot1 missing.
>
> mdadm --create /dev/md0 /dev/sd[ac] -n 2 -e imsm
> mdadm --create /dev/md1 /dev/sda missing /dev/sdc -n 3 -l 5
>
> However, during this process I wanted to make sure I could get back to
> the exact same metadata that was on the disks, to root cause what went
> wrong, examine the metadata offline, or backup a step if I made a
> mistake in the recovery process. Patch9 implements --dump support, the
> fact that something like this has not been implemented already is maybe
> a clue that it is not such a great idea? I can imagine someone messing
> up their configuration if they restored a metadata image to the wrong
> device, but if you know what you are doing it could be a useful hack.
>
> ---
>
> Dan Williams (9):
> imsm: fix max disks per array
> imsm: fix, stop metadata updates to newly failed devices
> imsm: fix display spares
> sysfs: fix sysfs_disk_to_scsi_id
> imsm: fix reserved sectors for spares
> mdmon: fix, close spare activation race
> imsm: support 'missing' devices at Create
> util: allow regular files through test_partition()
> mdadm: 'dump' support
>
>
> Examine.c | 42 ++++++++++++++++
> ReadMe.c | 1
> managemon.c | 5 ++
> mdadm.8.in | 13 +++++
> mdadm.c | 11 ++++
> mdadm.h | 3 +
> super-intel.c | 146 +++++++++++++++++++++++++++++++++++++--------------------
> sysfs.c | 30 ++++--------
> util.c | 6 ++
> 9 files changed, 182 insertions(+), 75 deletions(-)
Thanks.
I've applied all but the last two - which I might want done slightly
differently as discussed already.
I also fixed a build breakage in "make everything" .... though maybe I should
get rid of mdassemble - it is hard to maintain and I'm not really sure that
it is useful.
Thanks,
NeilBrown
prev parent reply other threads:[~2011-08-30 3:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 2:13 [PATCH 0/9] recovering an imsm raid5 array Dan Williams
2011-08-26 2:14 ` [PATCH 1/9] imsm: fix max disks per array Dan Williams
2011-08-26 2:14 ` [PATCH 2/9] imsm: fix, stop metadata updates to newly failed devices Dan Williams
2011-08-26 2:14 ` [PATCH 3/9] imsm: fix display spares Dan Williams
2011-08-26 2:14 ` [PATCH 4/9] sysfs: fix sysfs_disk_to_scsi_id Dan Williams
2011-08-26 2:14 ` [PATCH 5/9] imsm: fix reserved sectors for spares Dan Williams
2011-08-26 19:51 ` Williams, Dan J
2011-08-30 2:20 ` NeilBrown
2011-09-06 20:42 ` Williams, Dan J
2011-09-19 12:57 ` Czarnowska, Anna
2011-09-21 4:45 ` NeilBrown
2011-08-26 2:14 ` [PATCH 6/9] mdmon: fix, close spare activation race Dan Williams
2011-08-26 2:14 ` [PATCH 7/9] imsm: support 'missing' devices at Create Dan Williams
2011-08-30 2:26 ` NeilBrown
2011-08-26 2:14 ` [PATCH 8/9] util: allow regular files through test_partition() Dan Williams
2011-08-26 2:14 ` [PATCH 9/9] mdadm: 'dump' support Dan Williams
2011-08-30 2:58 ` NeilBrown
2011-08-30 10:12 ` Alexander Kühn
2013-05-16 5:11 ` NeilBrown
2011-08-26 11:06 ` [PATCH 0/9] recovering an imsm raid5 array linbloke
2011-08-30 3:13 ` NeilBrown [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=20110830131331.02adf4c2@notabene.brown \
--to=neilb@suse.de \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=marcin.labun@intel.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).