FWIW, I also tested this on a similar KVM instance using a SCSI disk device and installed Ubuntu using LVM, running the same test case does not result in the failure; even though write_same is enabled for those devices.
ubuntu@lp1371591:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 30G 0 disk ├─sda1 8:1 0 243M 0 part /boot ├─sda2 8:2 0 1K 0 part └─sda5 8:5 0 29.8G 0 part ├─lp1371591--vg-root (dm-0) 252:0 0 28.8G 0 lvm / └─lp1371591--vg-swap_1 (dm-1) 252:1 0 1G 0 lvm [SWAP] sr0 11:0 1 1024M 0 rom ubuntu@lp1371591:~$ cat /sys/block/dm-*/queue/write_same_max_bytes 33553920 33553920 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371591 Title: file not initialized to 0s under some conditions on VMWare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
