On 12/03/2014 05:00 PM, Martin K. Petersen wrote: > Mike> Jazz@xxxxxxxxx's patch would work around the same problem because > Mike> in sd_read_write_same, sd would see no_write_same is set and not > Mike> send REPORT SUPPORTED OPERATION. > > Yeah. > > I still don't have a problem quirking the MS target. As long as I can > get good strings and revs to match on. Obviously setting no_write_same > for all iSCSI targets is a no-go. Shooooot, not sure what was tested in that thread now. I tried out the newer MS iscsi target, 3.3, and still hit the same issue that was reported here. What info did you need? Here is vendor/product/version info: Vendor identification: MSFT Product identification: Virtual HD Product revision level: 3.3 -- 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
