Hi Moussa, On Thu, 2014-05-22 at 21:35 +0000, Moussa Ba (moussaba) wrote: <SNIP> > > > > > > Looks like the issue was HardwareAcceleration in esx...Essentially we > > > would get the timeouts when trying to create a VM Thick Provisioned > > > Eager Zero which translated into esx sending a WRITE_SAME command. > > > Jared was doing a wireshark capture when he noticed that. > > > > > > This reminded me that we had to disable the HardwareAcceleration in > > > esx when we were doing VMMark last year. By default, these values > > are > > > enabled and LIO seems to advertise that it supports hardware > > > acceleration based on the datastore characteristics in ESX. > > > > > > > > > VMFS3.HardwareAcceleratedLocking > > > DataMover.HardwareAcceleratedMove > > > DataMover.HardwareAcceleratedInit > > > > > > As soon as we disabled them, no more time out issues... > > > > Ah yes, thanks for confirming. > > > > > I believe WRITE_SAME/XCOPY and ATS only made it into LIO in 3.14? > > > > So WRITE_SAME support for IBLOCK went in v3.6, along with generic > > EXTENDED_COPY + COMPARE_AND_WRITE support in v3.12. > > > > > The question I have is where does this information belong and how can > > > one debug these issues... > > > > > > > FYI, these VAAI primitives can also be disabled target side with device > > attributes: > > > > emulate_caw=0 > > emulate_3pc=0 > > max_write_same_len=0 > > > > To debug, please try ESX host settings Init=0 + Move=1 + Locking=1 to > > see if it's specific to WRITE_SAME, and separately if COMPARE_AND_WRITE > > traffic can also trigger the bug.. > > Setting Init=0, Move=1 and Locking=1 does not create the time out > issue. So so far it seems the issues is specific to WRITE_SAME. I > will > Great, thanks for the update. > > > > Also, what do the negotiated ImmediateData + InitialR2T parameter > > settings look like..? > > Both are set to yes. I am reading these off of /sys/kernel/config/.../iqn..../param/ > > OK, I'll verify WRITE_SAME works as expected with the Linux iSER initiator, and from there it should be clear if it's a bug specific to ESX iSER initiator code. --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
