linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Troy Telford <ttelford.groups@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: RAID-6 disk superblock issue
Date: Wed, 14 Dec 2011 14:41:52 -0700	[thread overview]
Message-ID: <jcb570$1do$1@dough.gmane.org> (raw)
In-Reply-To: 4EE8F26D.7010608@turmel.org

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.)

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.

> 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.
-- 
Troy Telford



  reply	other threads:[~2011-12-14 21:41 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 [this message]
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='jcb570$1do$1@dough.gmane.org' \
    --to=ttelford.groups@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).