From: NeilBrown <neilb@suse.de>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Upgrading from metadata 0.9
Date: Sat, 28 May 2011 07:38:53 +1000 [thread overview]
Message-ID: <20110528073853.2b9ead34@notabene.brown> (raw)
In-Reply-To: <4DDEA8AB.4090709@cfl.rr.com>
On Thu, 26 May 2011 15:23:23 -0400 Phillip Susi <psusi@cfl.rr.com> wrote:
> Is there a way to upgrade an existing raid array using metadata format
> 0.9 to a 1.x format without loosing data?
Not really. It is on my list of nice-to-have features for mdadm, but it is
not near the top.
As 1.x uses less space for metadata you could simply recreate the array as
--metadata=1.0
All the data would still be there.
You should be as explicit as possible in the --create command.
mdadm --create /dev/md0 --level=XX --raid-disks=YY --chunk=ZZ --size=QQ
--layout=LL --assume-clean --metadata=1.0
You can only convert to 1.0 metadata as 1.1 and 1.2 put the metadata on top
of where data currently is.
NeilBrown
prev parent reply other threads:[~2011-05-27 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 19:23 Upgrading from metadata 0.9 Phillip Susi
2011-05-27 21:38 ` 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=20110528073853.2b9ead34@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=psusi@cfl.rr.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.