On Tuesday October 31, frido@xxxxxxxxxx wrote: > Hi, > > On Tue, Oct 31, 2006 at 08:50:19AM -0800, Mike Hardy wrote: > > >> 1 "Warm swap" - replacing drives without taking down the array but maybe > > >> having to type in a few commands. Presumably a sata or sata/raid > > >> interface issue. (True hot swap is nice but not worth delaying warm- > > >> swap.) > > > > > > I believe that 2.6.18 has SATA hot-swap, so this should be available > > > know ... providing you can find out what commands to use. > > > > I forgot 2.6.18 has SATA hot-swap, has anyone tested that? > > Yeah, I've tracked the sata EH patches and now 2.6.18 for a while and > hotswap works. However if you pull the disk on a raidset the disk is set > as faulty and the device (/dev/sda for example) dissapears. If you > replug it, the device does not regain it's original devicename but but > will use the latest free 'slot' available (in a four disk layout that's > /dev/sde). Also trying to --remove the disk doesn't work since the > devicefile is gone. So be sure to --remove disks _before_ you pull it. > > Anyone know if there's work being done to fix this issue, does > this also happen on scsi ? The 'correct' way to fix "--remove doesn't work after" is to get udev to do the "mdadm --remove" before deleting the entry from /dev. mdadm could probably be changed to be able to remove the device anyway. The only difficulty is: how do you tell it which device to remove", given that there is no name in /dev to use. Suggestions? Having the device come back with a different name shouldn't really be a problem. You can still find it an re-add it. 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
