Re: md metadata nightmare

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

 



Hi Ken,

On 11/22/2011 07:47 PM, NeilBrown wrote:
> On Tue, 22 Nov 2011 18:05:21 -0600 Kenneth Emerson
[...]
> Assuming nothing has changed since the "--detail" output you provided, you
> should:
> 
>  mdadm -S /dev/md3
>  mdadm -C /dev/md3 --metadata=1.0 --chunk=64k --level=6 --raid-devices=5 \
>       missing /dev/sdb4 /dev/sdc4 /dev/sda4 /dev/sdd4 \
>       --assume-clean
> 
> The order of the disks is import.  You should compare it with the output
> of "mdadm --detail" before you start to ensure that it is correct and I have
> made any typos.  You should of course check the rest as well.
> After doing this (and possibly before) you should 'fsck' to ensure the
> transition was successful.  If anything goes wrong, ask before risking
> further breakage.

A word of warning...  the shell notation /dev/sd[bcad]4, which you might be
tempted to type in the above command line, *will* *not* *work*.  Bash reorders
the [bcad] to [abcd], dropping nonexistent names.  You might know this, and
not be burned, but others on the list have been.  Use {b,c,a,d} to stay safe.

HTH,

Phil
--
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