Hello folks, I have encountered the following problem while running our SAS driver with libsas: If we hot-unplug a drive that was attached via an expander, libsas starts sas_revalidate_domain() and discovers that the expander phy is empty. Then libsas starts to remove the device, eventually calls the sd layer that tries to synchronize cache. Synchronization retries cause a significant delay before libsas finally call SAS driver with sas_notify_lldd_dev_gone(). Some time ago there was a fix proposal for libsas: "Don't issue commands to devices that have been hot-removed" http://www.mail-archive.com/linux-scsi@xxxxxxxxxxxxxxx/msg12110.html but as I understand it was not accepted... Isn't it a bug? Should libsas forward commands to devices that are known to be missing? I'll appreciate any feedback. Thanks, Maciek Trela. -- 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
