On 08/29/14 08:19, Hannes Reinecke wrote: > On 08/29/2014 04:42 AM, Mike Christie wrote: >> How are distros handling 0x6/0x3f/0x0e (report luns changed) when it >> gets passed to userspace? Is everyone kicking off a new full (add and >> delete) scan to handle this or logging it? Is the driver returning this >> when the LUNs change? >> > Currently it's logged to userspace and ignored. > Doing an automated rescan has proven to be dangerous, as it > might disconnect any LUNs which are still in use by applications. > Especially HA or database setups tends to become very annoyed > when you do an automated rescan.
Has it already been considered to add newly discovered LUNs automatically and to leave it to the user to remove stale LUNs manually ? That would be similar to what the rescan-scsi-bus.sh script does without option -r/--remove. Bart. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
