From: NeilBrown <neilb@suse.de>
To: Troy Telford <ttelford.groups@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID-6 disk superblock issue
Date: Thu, 15 Dec 2011 09:07:51 +1100 [thread overview]
Message-ID: <20111215090751.3801a75a@notabene.brown> (raw)
In-Reply-To: <jcb570$1do$1@dough.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1854 bytes --]
On Wed, 14 Dec 2011 14:41:52 -0700 Troy Telford <ttelford.groups@gmail.com>
wrote:
> On 2011-12-14 19:01:01 +0000, Phil Turmel said:
>
> > Hi Troy,
> >
> > On 12/13/2011 05:42 PM, Troy Telford wrote:
> >
> > Let me guess: You have version 0.90 superblock, and sdl1 covers the
> > whole device?
>
> sdl1 does cover the entire device, but I'm fairly certain I do not have
> a 0.90 superblock (Unless 0.90 was the standard version for Linux 2.6
> about two years ago.)
It is mdadm that determines the superblock rather than the kernel, but you
definitely have 0.90 superblocks - I can tell from the /proc/mdstat output
(it doesn't list a version, so it must be 0.90).
>
> Unfortunately, I'm not sure how to get my current superblock version:
> $ sudo mdadm --examine /dev/md2
> mdadm: No md superblock detected on /dev/md2.
>
> I find it curious that I can't detect the superblock for the MD device,
> even though the device is up, active, and working.
The array doesn't have a superblock. Each member device does.
mdadm --examine /dev/sdl1
>
> > 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]
>
> OK, I'll give that a whirl. For the record, it was DEVICE partitions
> previously.
>
> > Then rebuild your initramfs to include the new mdadm.conf.
> >
> > Long term, rebuild your array with v1.x metadata.
>
> You know, I was hoping to be able to wait until btrfs handles RAID-6
> (or "raid-z") arrays by the time I had to rebuild the array. I guess
> I'm not that lucky.
You don't really need to rebuild the array. Just change the DEVICE line and
all will be happy.
(but I advise you never to plan on using software that hasn't be released yet
- that way lies madness).
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-12-14 22:07 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
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 [this message]
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=20111215090751.3801a75a@notabene.brown \
--to=neilb@suse.de \
--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 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).