Re: BLKZEROOUT not zeroing md dev on VMDK

From: Sitsofe Wheeler
Date: Fri May 27 2016 - 00:45:52 EST

On 27 May 2016 at 05:18, Darrick J. Wong <darrick.wong@xxxxxxxxxx> wrote:
> It's possible that the pvscsi device advertised WRITE SAME, but if the device
> sends back ILLEGAL REQUEST then the SCSI disk driver will set
> write_same_max_bytes=0. Subsequent BLKZEROOUT attempts will then issue writes
> of zeroes to the drive.

Thanks for following up on this but that's not what happens on the md
device - you can go on to issue as many BLKZEROOUT requests as you
like but the md disk is never zeroed nor is an error returned.

I filed a bug at
(see for
alternative reproduction steps that use scsi_debug and can be reworked
to impact device mapper) and Shaohua Li noted that
blkdev_issue_write_same could return 0 even when the disk didn't
support write same (see ).

Shaohua went on to create a patch for this ("block: correctly fallback
for zeroout" - ) which has
yet to be reviewed.

Sitsofe |