From: Neil Brown <neilb@suse.de>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm / RAID, a few questions
Date: Sat, 30 Oct 2010 07:44:08 +1100 [thread overview]
Message-ID: <20101030074408.05392452@notabene> (raw)
In-Reply-To: <AANLkTi=QRfQhNy5jDdtq2FsjENZk-ihNas=D4QrS2XMd@mail.gmail.com>
On Fri, 29 Oct 2010 15:18:09 +0100
Mathias Burén <mathias.buren@gmail.com> wrote:
> Question 3: Before I created this RAID5 array I did a quick RAID0 test
> array just for fun, using 2 full devices (not partitions). Now I have
> this:
>
> mdadm --examine --verbose --scan
> ARRAY /dev/md/raid0-test level=raid0 metadata=1.2 num-devices=2
> UUID=b84cc081:1ae27b49:d5ae466c:377ba300 name=ion:raid0-test
> devices=/dev/sdf,/dev/sdb
> ARRAY /dev/md/0 level=raid5 metadata=1.2 num-devices=6
> UUID=e6595c64:b3ae90b3:f01133ac:3f402d20 name=ion:0
> devices=/dev/sdg1,/dev/sdf1,/dev/sde1,/dev/sdd1,/dev/sdc1,/dev/sdb1
>
> Is it safe to erase the raid0-test superblocks on device /dev/sdb and
> /dev/sdc or will it interfere with my RAID5 array (which is lying on
> top of partitions) ?
It should be safe to
mdadm --zero-superblock /dev/sdf /dev/sdb
As you have 1.2 metadata, that info will be 4K from the start of the device.
Depending on how you partitioned the devices, that is either in dead space
between the partition table and the first partition, or it is in dead space
in the first partition just before the md metadata.
So the old metadata is still visible, creating the new arrays clearly didn't
over-write it, so they don't really care what is there...
That statement isn't 100% general. A block in the data area of the new array
could be unchanged by creating an array, yet changing it could still corrupt
parity. However you can be certain that the metadata for a whole-device
array does not lie in the data area for a partitioned array of the same
metadata type.
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-10-29 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 14:18 mdadm / RAID, a few questions Mathias Burén
2010-10-29 20:22 ` John Robinson
2010-10-29 20:35 ` Mathias Burén
2010-10-29 20:44 ` Neil Brown [this message]
2010-11-04 20:02 ` Mathias Burén
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=20101030074408.05392452@notabene \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@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 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).