On Tue, 2016-09-13 at 22:08 +0530, Gurunath, Vasundhara wrote: > From: "Gurunath, Vasundhara" <vasundhara.gurunath@xxxxxxx> > > SCSI block device can be removed, using write to sysfs > delete file as below: > echo 1 > /sys/block/sdX/device/delete > If the device is in use by applications, or part of > system configuration such as boot device, removal can > result in application disruptions or system down time. > > An additional write option ? is added to SCSI sysfs > interface as below, in order to prevent accidental > deletion of devices in use. > echo ? > /sys/block/sdX/device/delete > > In the absence of any usage, this option proceeds with > device deletion. If the device is open, deletion is > prevented, and active Open and IO counts at the time of > deletion is logged. Information logged during latest > delete attempt can be obtained by issuing a read to the > delete file as below: > cat /sys/block/sdX/device/delete OK, so I'm not too keen on this because our entire system is (finally) designed to be hot plug, so echoing 1 to delete simulates a hotplug event, and they can come in at any time. Can you elaborate on why this is necessary? Right at the moment, only root is allowed to write to this file and cause a deletion ... plus the file is pretty hard to find, buried as it is in sysfs; So I would have thought it was pretty safe from accidental misuse; why does it need additional protection? James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
