Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Rob Vandermeulen <rob.vandermeulen@telenet.be>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Missing md superblock on added devices after grow ...
Date: Sun, 24 May 2009 18:15:20 +0200	[thread overview]
Message-ID: <200905241815.20737.rob.vandermeulen@telenet.be> (raw)
In-Reply-To: <16efced97de975092f941a9a626d6f0d.squirrel@neil.brown.name>

Well, I found my error thanks to your comments about dm. While it's true that 
the /dev/mapper/sdxx devices are the same as /dev/sdxx , in my case this 
wasn't entirely true, as the disks i added had a primary partition on them, 
but i deleted them and made that primary partition a little smaller. However, 
dm mappings are only loaded on boot normally, so these were not reloaded . 
Result : the reshape took place on the older "larger" partitions instead of 
the new, slightly smaller ones. Ofcourse, the superblock was in that area too 
ofcourse. I restored the partitions to their original larger size and was able 
to get the superblocks read, and have succesfully recreated a degraded 7 disk 
array and all data is still intact :)

I guess i really should be more carefull using mapper and real devices when 
changing partition layout.

Thanks for the assistance.

On Saturday 23 May 2009 23:05:35 you wrote:
> On Sun, May 24, 2009 1:03 am, rdc wrote:
> > Yesterday i grew my 4*500GB raid5 array to 7*500GB. The reshape operation
> > ended succesfully according to the logs :
> >
> > May 22 22:24:56 [kernel] md: md2: reshape done.
> > May 22 22:24:56 [kernel] RAID5 conf printout:
> > May 22 22:24:56 [kernel]  --- rd:7 wd:7
> > May 22 22:24:56 [kernel]  disk 0, o:1, dev:dm-3
> > May 22 22:24:56 [kernel]  disk 1, o:1, dev:dm-0
> > May 22 22:24:56 [kernel]  disk 2, o:1, dev:dm-2
> > May 22 22:24:56 [kernel]  disk 3, o:1, dev:dm-1
> > May 22 22:24:56 [kernel]  disk 4, o:1, dev:dm-8
> > May 22 22:24:56 [kernel]  disk 5, o:1, dev:dm-6
> > May 22 22:24:56 [kernel]  disk 6, o:1, dev:dm-5
>
> The devices in your array are dm-xx devices, but....
>
> > However, upon restarting this morning the grown array was no longer
> > detected,
> > and my investigation revealed that the 3 device that were added do not
> > contain
> > an md superblock at all !
> >
> > One of the 3 new devices :
> > mdadm --examine -v /dev/sdb1
> > mdadm: No md superblock detected on /dev/sdb1.
>
> ... you are looking on sdxx devices for the superblock.  This
> seem to me to be a strange thing to do.
> What does
>    mdadm --example /dev/mapper/whatever
> show?
>
> What exactly are the dm-xx devices?
>
> NeilBrown


  parent reply	other threads:[~2009-05-24 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-23 15:03 Missing md superblock on added devices after grow rdc
2009-05-23 21:05 ` NeilBrown
2009-05-24 13:49   ` rdc
2009-05-24 16:15   ` Rob Vandermeulen [this message]
2009-05-24 18:06     ` Billy Crook

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=200905241815.20737.rob.vandermeulen@telenet.be \
    --to=rob.vandermeulen@telenet.be \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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