Messages in this thread | | | From | "Zengtao (B)" <> | Subject | RE: scsi_set_medium_removal timeout issue | Date | Wed, 14 Nov 2018 02:46:27 +0000 |
| |
Hi Alan:
>-----Original Message----- >From: Alan Stern [mailto:stern@rowland.harvard.edu] >Sent: Monday, November 12, 2018 11:33 PM >To: Zengtao (B) <prime.zeng@hisilicon.com> >Cc: jejb@linux.vnet.ibm.com; martin.petersen@oracle.com; >gregkh@linuxfoundation.org; linux-scsi@vger.kernel.org; >linux-kernel@vger.kernel.org; linux-usb@vger.kernel.org; >usb-storage@lists.one-eyed-alien.net >Subject: RE: scsi_set_medium_removal timeout issue > >On Mon, 12 Nov 2018, Zengtao (B) wrote: > >> >> >Something is wrong here. Before sending PREVENT-ALLOW >MEDIUM >> >> >REMOVAL, the host should issue SYNCHRONIZE CACHE. This will >force >> >> >fsg_lun_fsync_sub to run, and the host should allow a long timeout >> >> >for this command. Then when PREVENT-ALLOW MEDIUM >REMOVAL >> >is sent, >> >> >nothing will need to be flushed. >> >> > >> >> >> >> Definitely, I haven't seen the SYNCHRONIZE CACHE from the host, it >> >> directly issued the PREVENT-ALLOW MEDIUM REMOVAL, so maybe >> >something >> >> wrong with the scsi layer or something wrong with the mass storage >> >class driver? >> > >> >Or it could be something else. Can you please post the dmesg log >> >from the host, showing what happens when the device is first plugged >in? >> > >> >> I have enabled the SCSI log for the host, please refer to the attachment. > >The log you attached was incomplete -- it was missing some commands
I just enabled the scsi log in the middle of the umount operation, otherwise I can't reproduce the issue when the scsi log is enabled.
>from the beginning. In any case, it wasn't what I wanted. I asked you to >post the dmesg log, not the SCSI log.
Please refer to the new attachment for dmesg log.
Thanks Zengtao
| |