From: Phil Turmel <philip@turmel.org>
To: Troy Telford <ttelford.groups@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID-6 disk superblock issue
Date: Wed, 14 Dec 2011 14:01:01 -0500 [thread overview]
Message-ID: <4EE8F26D.7010608@turmel.org> (raw)
In-Reply-To: <jc8kca$mf$1@dough.gmane.org>
Hi Troy,
On 12/13/2011 05:42 PM, Troy Telford wrote:
> I have a RAID-6 array I'm having trouble with:
>
> md2 : active raid6 sdl1[6] sdh1[0] sdm1[5] sdk1[3] sdj1[2] sdi1[1]
> 1953535488 blocks level 6, 128k chunk, algorithm 2 [6/5] [UUUU_U]
> [>....................] recovery = 0.0% (27164/488383872) finish=599.1min speed=13582K/sec
>
> - When the system boots (or when I attempt to build the array), I get a message that /dev/sdl and /dev/sdl1 have the same superblock, and that I should zero one.
> - So, I zero the superblock using 'mdadm --zero-superblock /dev/sdl (or /dev/sdl1; doesn't matter which I use).
> - I then re-add the device to the array (and the RAID-6 array recovers, as above.)
> - The next time I boot, I get the exact same error message.
>
>
> - It doesn't seem to matter which (between the device or the partition) that I zero the superblock on. I get the same error message at boot (when the drive is being assembled).
> - Since it's redundant data anyway, I've tried dd'ing from /dev/zero over the drive, repartitioning the drive, and then adding the drive to the array. Same behavior.
>
> - My mdadm.conf just has the array itself, and the array's UUID. It doesn't explicitly list devices.
>
> So what am I missing? There's got to be a way I can get the array to assemble at boot, instead of having to manually --zero-superblock every time.
Let me guess: You have version 0.90 superblock, and sdl1 covers the whole device?
Short term, change your mdadm.conf to only accept device names that end with a digit. Like so:
DEVICE /dev/sd[a-z][1-9]
Then rebuild your initramfs to include the new mdadm.conf.
Long term, rebuild your array with v1.x metadata.
HTH,
Phil
next prev parent reply other threads:[~2011-12-14 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 22:42 RAID-6 disk superblock issue Troy Telford
2011-12-14 19:01 ` Phil Turmel [this message]
2011-12-14 21:41 ` Troy Telford
2011-12-14 22:04 ` Mark Knecht
2011-12-14 22:08 ` Troy Telford
2011-12-14 22:07 ` NeilBrown
2011-12-14 22:14 ` Troy Telford
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=4EE8F26D.7010608@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=ttelford.groups@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 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.