Re: grow fails with 2.6.34 git

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 14 Apr 2010 19:22:48 -0700
Michael Evans <mjevans1983@xxxxxxxxx> wrote:

> On Wed, Apr 14, 2010 at 6:04 PM, Neil Brown <neilb@xxxxxxx> wrote:
> > What is happening here is that the spare (sdh) is getting the Q blocks
> > written to it.  When this completes you will have full 2-disk redundancy but
> > the layout will not be optimal and the array wont be any bigger.
> > To fix this you would:
> >
> >  mdadm --grow --backup-file=/root/backup.md4 --raid-devices=6 \
> >      --layout=normalise /dev/md4
> >
> 
> Is there some way of telling if the layout is proper, or is that what
> 'level 6' indicates?

mdadm -D  should list the layout.
If it ends "-6" then it is a non-standard layout with Q on the last device
and the remainder of the devices laid out like a RAID5.

> 
> Also is it safe to run something like...
> 
> mdadm --grow --back-file=/some/never/used/file --layout=normalize /dev/mdX
> 
> on any raid 5/6 device that isn't undergoing an active reshape? (would
> it be a null-op if not required)

Yes.  It quite literally looks at the layout name to see if it ends with "-6".
If it is not needed it will actually report and error:
mdadm: layout normalize not understood for raid6.

I should probably fix that.....  one day.

NeilBrown

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux