From: Neil Brown <neilb@suse.de>
To: Greg Cormier <gcormier@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Superblocks
Date: Tue, 30 Oct 2007 15:27:42 +1100 [thread overview]
Message-ID: <18214.45758.794247.651163@notabene.brown> (raw)
In-Reply-To: message from Greg Cormier on Friday October 26
On Friday October 26, gcormier@gmail.com wrote:
> Can someone help me understand superblocks and MD a little bit?
>
> I've got a raid5 array with 3 disks - sdb1, sdc1, sdd1.
>
> --examine on these 3 drives shows correct information.
>
>
> However, if I also examine the raw disk devices, sdb and sdd, they
> also appear to have superblocks with some semi valid looking
> information. sdc has no superblock.
If a partition starts a multiple of 64K from the start of the device,
and ends with about 64K of the end of the device, then a superblock on
the partition will also look like a superblock on the whole device.
This is one of the shortcomings of v0.90 superblocks. v1.0 doesn't
have this problem.
>
> How can I clear these? If I unmount my raid, stop md0, it won't clear it.
mdadm --zero-superblock device name
is the best way to remove an unwanted superblock. Ofcourse in the
above described case, removing the unwanted superblock will remove the
wanted one aswell.
>
> [root@zeus ~]# mdadm --zero-superblock /dev/hdd
> mdadm: Couldn't open /dev/hdd for write - not zeroing
As I think someone else pointed out "/dev/hdd" is not "/dev/sdd".
NeilBrown
next prev parent reply other threads:[~2007-10-30 4:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 16:43 Superblocks Greg Cormier
2007-10-27 14:08 ` Superblocks Raz
2007-10-30 4:27 ` Neil Brown [this message]
2007-10-30 16:06 ` Superblocks Greg Cormier
2007-11-01 23:29 ` Superblocks Neil Brown
2007-11-02 12:33 ` Superblocks Bill Davidsen
2007-11-02 14:15 ` Superblocks Greg Cormier
2007-11-03 13:49 ` Superblocks Bill Davidsen
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=18214.45758.794247.651163@notabene.brown \
--to=neilb@suse.de \
--cc=gcormier@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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).