Hi All, We are running a test case of SAS cable pull/push on a SAS RAID system. After the SAS cable is pulled from a SAS RAID, scsi devices are deleted. And then when the cable is pushed back, the scsi device with the same H:C:T:L sometime will be assigned to a diffent sgX. Reading through the sg.c, it seems that if the sg device has a pending write request, the sg slot (sg_dev_arr[k] = NULL) will not be freed during sg_remove time. Can someone confirm this? If this is the case, what the user space process do to prevent this from happening? I see that the sg.c sends SIGPOLL to the user space process (kill_fasync(&sfp->async_qp, SIGPOLL,POLL_HUP);), what this signal will be translated to the user space return-code from read/write call? Thanks, Yanling - 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
