Re: iSCSI request keep rejected by microsoft iSCSI target because of write_same check

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> "Mike" == Mike Christie <michaelc@xxxxxxxxxxx> writes:

>> 2. report_opcode is optional in SPC-3, so it's possible that not all
>> iscsi target support it. But is it correct for microsoft iSCSI target
>> to reject the command rather than return it with normal SCSI
>> response?

Mike> The iscsi spec has the reason code "command not supported" so I
Mike> guess it is ok for the target to do this. I do not think I have
Mike> ever seen that reason code used in production level targets, so it
Mike> is probably not common.

It's kind of unfriendly to not send a check condition...


Mike> I think we should implement handling in the iscsi layer for it. I
Mike> can make a patch if you have not already.

It would be awfully nice to get it turned into an ILLEGAL
REQUEST/0x20/0x0.

-- 
Martin K. Petersen	Oracle Linux Engineering
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux