On 04/22/2014 04:10 AM, Cale, Yonatan wrote: > -----Original Message----- > From: Mike Christie [mailto:[email protected]] > Sent: Tuesday, April 22, 2014 12:38 AM > To: Cale, Yonatan > Cc: [email protected]; [email protected] > Subject: Re: Target reboot -> iscsiadm rescan Stuck > >> Do you have some module that is hooking into the scsi layer or iscsi >> modules? Just wondering what the "sim_try_to_abort_cmd" call is. Where are >> you hooking in? > "sim" is our module that handles iscsi data-path. We hook for notifications > in order to know if we should cancel a command
Hey, does your sim module that handles the data path just monitor or do you handle error codes that the iscsi modules returns. The problem is that the iscsi layer is trying to fail a scsi scan related command, but whatever layer is above it (I thought it was just the scsi layer like normal in my other response) just keeps retrying it. Does your module do anything to IO failed with #define DID_TRANSPORT_FAILFAST 0x0f /* Transport class fastfailed the io */ from the queuecommand path? Is it the one forcing the retry? That would explain why we do not see anything from the scsi scan layer debug printks. If not, then it is the scsi or block layer and we will have to add some printks in there. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
