|
|
|
Re: mdadm.conf unnecessary? | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
Dexter Filmore wrote:
So the new disks will be sd[efgh]1.But when I pull the old drives after migrating, they will be sd[abcd]1.. so... how do I handle this?
Make an mdadm.conf file that reflects your current array and use UUID's to identify the arrays - here is an example:
ARRAY /dev/md5 level=raid5 num-devices=4 UUID=32cd6355:3c2c08a3:970a9f77:c13e51a3
Note, this should be all one line.This will ensure that regardless of which /dev/sdX a drive is, the array will be assembled only from drives which are using this UUID.
mdadm -D /dev/mdX where X is your current array will give you the UUID of this array.
Regards, Richard -- 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
[Home] [ATA RAID] [Linux SCSI Target Infrastructure] [Linux] [Managing RAID on Linux] [Linux IDE] [Linux SCSI] [Linux Hams] [Device-Mapper] [Kernel] [Linux Books] [Linux Admin] [Linux Net] [GFS] [RPM] [Photos] [Yosemite Photos] [Yosemite News] [AMD 64] [Linux Nework]
![]() |
![]() |