On 12/03/2014 05:00 PM, Martin K. Petersen wrote: > Mike> [email protected]'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 -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
