Re: MD device id change

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

 



On Friday April 4, mblack@csi-inc.com wrote:
> Here's one I've run into Neil -- Put an already-running md on another system with the same minor #.
> 
> Can you start the new md and not have to stop the old one?
> 
> i.e.
> /dev/md2 on system#1
> /dev/md2 on system#2
> move /dev/md2 chassis to system#2
> 
> Would this work?
> mdadm --assemble --uuid=MOVED_MD2 --super-minor=2 /dev/md3

You would need to tell mdadm that devices to look at, possibly
using --config=partitions, but that would work to assemble the array.
> 
> And would the array now stay as md3?

Not in 2.4 (though in 2.5 it would).

You need --update=super-minor for that to happen.  Ofcourse if you use
mdadm for assembling arrays and always use UUID, then you don't need
to convern yourself with the minor number in the superblock at all.

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
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