On 27 May 2016 at 10:30, Tom Yan <tom.ty89@xxxxxxxxx> wrote: > There seems to be some sort of race condition between > blkdev_issue_zeroout() and the scsi disk driver (disabling write same > after an illegal request). On my UAS drive, sometimes `blkdiscard -z > /dev/sdX` will return right away, even though if I then check > `write_same_max_bytes` it has turned 0. Sometimes it will just write > zero with SCSI WRITE even if `write_same_max_bytes` is 33553920 before > I issue `blkdiscard -z` (`write_same_max_bytes` also turned 0, as > expected). > > Not sure if it is directly related to the case here though. I'm not aware of hitting that particular problem myself directly on the underlying "SCSI" device but the patch on https://patchwork.kernel.org/patch/9137311/ should be able to resolve that issue. Could you test it and follow up on http://permalink.gmane.org/gmane.linux.kernel/2229377 ? I'm hoping more testing reports will lead to the patch being reviewed and accepted sooner rather than later as it's currently stalled... -- Sitsofe | http://sucs.org/~sits/ -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
