Hello, Tim Small wrote: > " > For reliable device removal notification while in AHCI operation without > the use of interlock switches (surprise removal), interface power > management should be disabled for the associated port. See Section 7.3.1 > of the AHCI Specification for more information. > " > > Is this actually an issue from a libata point of view? Do I need to > ensure that link power management is disabled prior to hot-removal, and > if so, I suppose link_power_management_policy.txt should be updated to > reflect this... Yeap, libata wouldn't know the device is yanked out. It will find out later when it tries to issue a command later tho. It could be a problem if you hot-swap the drive. libata wouldn't know that devices have been exchanged. > On a related topic, is there any way to do anything other than > "surprise" removal with libata? It'd be nice to put a drive to sleep > (e.g. with "hdparm -Y"), and ensure that nothing comes along and causes > the drive to be reset and spin the drive attached to that SATA port back > up prior to a removal and reinsertion. echo 1 > /sys/block/sdX/device/delete > I'm assuming that physically unplugging a non-spinning drive is > preferable to unplugging a spinning one from a drive longevity point of > view (I use SATA drives as removable backup medium in some cases). Yeah, you'll induce an emergency unload if you remove power while the drive is spinning, but drives are designed to deal with certain number of those events and if it doesn't happen regularly, you don't need to worry about it. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
