From: linbloke <linbloke@fastmail.fm>
To: Dan Williams <dan.j.williams@intel.com>
Cc: neilb@suse.de, linux-raid@vger.kernel.org,
marcin.labun@intel.com, ed.ciechanowski@intel.com
Subject: Re: [PATCH 0/9] recovering an imsm raid5 array
Date: Fri, 26 Aug 2011 21:06:22 +1000 [thread overview]
Message-ID: <4E577E2E.2070903@fastmail.fm> (raw)
In-Reply-To: <20110826020908.28015.52384.stgit@localhost6.localdomain6>
On 26/08/11 12:13 PM, Dan Williams wrote:
<snip>
> 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.
>
I'm just a nobody mdadm user but I read nearly every word of this list
and read the above and thought, if Dan thinks it's a good idea, then it
probably is. I then read the summary of Patch 9, included below and
thought, this might be safer if it required a --force switch to actually
make the change, force usually being a sign that the user knows what
they are doing (;-) Perhaps without it, it could just check that foo is
valid (identical size) and suggest the force switch to make it so. Sorry
I'm not a coder that can supply a patch, this compromise to deliver the
functionality but with a safeguard in place occurred to me.
Best regards and kudos to our linux developers.
mdadm -E /dev/sda --dump=foo
Creates a sparse file image of /dev/sda named foo with a copy of the
metadata instance found by -E.
When used in the opposite direction:
mdadm -E foo --dump=/dev/sda
...can restore metadata to a given block device, assuming it is
identical size to the dump file.
next prev parent reply other threads:[~2011-08-26 11:06 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 ` linbloke [this message]
2011-08-30 3:13 ` [PATCH 0/9] recovering an imsm raid5 array NeilBrown
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=4E577E2E.2070903@fastmail.fm \
--to=linbloke@fastmail.fm \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=marcin.labun@intel.com \
--cc=neilb@suse.de \
/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).