From: NeilBrown <neilb@suse.de>
To: "Alexander Kühn" <alexander.kuehn@nagilum.de>
Cc: Dan Williams <djbw@fb.com>,
linux-raid@vger.kernel.org, marcin.labun@intel.com,
ed.ciechanowski@intel.com
Subject: Re: [PATCH 9/9] mdadm: 'dump' support
Date: Thu, 16 May 2013 15:11:59 +1000 [thread overview]
Message-ID: <20130516151159.70fe0aee@notabene.brown> (raw)
In-Reply-To: <20110830121203.Horde.wvD-Spk8pphOXLdzcMjKT1A@cakebox.homeunix.net>
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
On Tue, 30 Aug 2011 12:12:03 +0200 Alexander Kühn
<alexander.kuehn@nagilum.de> wrote:
>
> Zitat von NeilBrown <neilb@suse.de>:
>
> > On Thu, 25 Aug 2011 19:14:45 -0700 Dan Williams <dan.j.williams@intel.com>
> > wrote:
> >
> >> 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.
> >
> > Suppose we did have a separate 'restore' function - what would it look like?
> > An option to create?
> >
> > mdadm --create --restore=some-directory /dev/sda /dev/sdb
> >
>
> Yes, from a UI perspective having separate dump/restore options is
> better. Since there is also dump(8)/restore(8) it would also keep the
> nomenclature.
> Otherwise I would rather name it "copy-metadata" or something as with
> copying the user is or should be aware that the order or arguments
> matters.
> Alex.
Nearly two years later, I've committed some functionality based on this.
mdadm --dump=/root/md /dev/*
will create files in /root/md/ with metadata from any device with metadata
recognised by mdadm.
mdadm --restore=/root/md /dev/*
will restore it all.
More details in the man page.
http://git.neil.brown.name/git?p=mdadm.git;a=blob;f=mdadm.8.in;h=c8559dae8e789a30e0c4ee826745a42980629977;hb=74db60b00a43a5ae636477c10c24e923e76049ce
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-05-16 5:11 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 [this message]
2011-08-26 11:06 ` [PATCH 0/9] recovering an imsm raid5 array linbloke
2011-08-30 3:13 ` 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=20130516151159.70fe0aee@notabene.brown \
--to=neilb@suse.de \
--cc=alexander.kuehn@nagilum.de \
--cc=djbw@fb.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).