On 01/23/2013 02:58 PM, Mike Christie wrote: > When you run the test, before IO is failed with that error, is the iscsi
Actually we want to know the state before and after. We would also want to know if the kernel is properly queueing IO at this time or is it retrying it somehow. Also the command that hit the timing out path might be some special IO and not READ/WRITE IO, because the max time is only 60 secs which is short of a normal FS/block READ/WRITE. The IO that got failed in the log you sent could be a SG IO, so maybe not relevant to the problem. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
