Comment 28 for bug 1371591

Revision history for this message
Petr Vandrovec (petr-vmware) wrote : Re: file not initialized to 0s under some conditions on VMWare

Hi Chris,
  can you revert original patch which blacklist VMware for no good reason, and instead apply attached patch, or its equivalent? As explained above, bug affects ALL disks that do not support WRITE_SAME when used with stackable block devices, like LVM. Due to the bug Linux kernel stops issuing WRITE_SAME after first failure, treating them as succeeding, instead of falling back to non-write-same code.

I have doubts about handling discards too, but I'm not Linux storage guru, so I left discard handling returning EOPNOTSUPP, rather than switching it to EREMOTEIO too.

Unfortunately I could not yet figure out how to reopen this bug so that correct fix can tracked.

Thanks,
Petr Vandrovec

Disclosure: I'm VMware employee.