Scenario: I have a file system on a USB SCSI disk /dev/sdb mounted on /mnt. I perform Action 1 below, and after some time, perform Action 2 below. Action 1: removal (unplug) of a USB disk At the time of removal of the USB disk, since the file system was mounted, is the reference to kobject corresponding (now orphaned) sdb still maintained in the kernel, although /dev/sdb is gone due to disk removal? Is it that the old scsi_disk (sdb) still persists, but, the underlying scsi_dev is removed? Where should I start to trace the hotplug removal of the USB disk? What are the specific processing steps involved in the kernel to handle this (in terms of main routines handling this)? Action 2: (hot) plug addition of the same USB SCSI disk On plugging in the same USB SCSI disk, does the sd layer in scsi subsystem grab the first available 'free' sdX device (say sdp), given that sdb is still being referenced by the mounted file system? Again, in terms of code, does this correspond to: - a new scsi_dev being allocated - a corresponding scsi_disk for sdp being allocated by the sd layer in scsi subsystem as part of 'probe' for the added SCSI device Does the hot plugging work the same way for SAS disks attached behind a FC switch? Thanks, - Kishore -- 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
