Hi Sergey, On Thu, 24 Jun 2021 14:19:25 +0300, Sergey Samoylenko wrote: > EXTENDED COPY tests in libiscsi [1] show that TCM doesn't > follow SPC4 when detects invalid parameters in a XCOPY > command or IO errors. The replies from TCM contain wrong sense > key or ASCQ for incorrect request. > > The series fixes the following tests from libiscsi: We've hit this too. The incorrect sense reporting appears to also affect VMware XCOPY fallback to initiator driven READ/WRITE. I'm pretty sure this is a regression from d877d7275be34ad70ce92bcbb4bb36cec77ed004, so should probably be marked as such via a Fixes tag. Cheers, David
