On Mon, 2012-02-13 at 14:28 -0800, Nicholas A. Bellinger wrote: > On Fri, 2012-02-10 at 20:25 -0800, Nicholas A. Bellinger wrote: > > On Thu, 2012-02-09 at 14:01 +0800, Jim Barber wrote: > > > On 9/02/2012 11:29 AM, Nicholas A. Bellinger wrote: <SNIP> > > Hi Jim, > > So with the patches from this morning to add support for TMR_ABORT_TASK, > I'd like you to try re-testing with ESXv5 client. > > At this point I'm pretty sure the reason you are seeing ABORT_TASK is > because your backend device is taking a long time (> 30 secs) to return > outstanding I/O, causing SCSI timeouts on the FC initiator to fire.. > I also forgot to mention that if your backends are expected to take a while before returning outstanding I/O, it might be worthwhile (after re-testing) with the new TMR_ABORT_TASK patches to increase the SCSI timeout value on the ESX FC initiator side in order to rule out client side false positives.. --nab -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
