On Nov 22, 2011, at 5:49 AM, Dave Chinner wrote: > But, I just noticed that the discard that mkfs.ext4 will result in > all the extents being discarded in the underlying image file (due to > the fact the loopback device now supports hole punching), so the > previous state of the image file is getting trashed by the mkfs.ext4 > execution, too. I think I already had a ext4 filesystem in some state > before I started running this manual prealloc test.... Which version of mkfs.ext4 are you using? We've disabled the discard by default (unless configured in via a command-line option or a /etc/mke2fs.conf setting since no distribution apparently wants to be responsible for running supplying a command that causes a crap SSD to turning into a brick; personally, I'd blame the manufacturer of the crap SSD, but….) -- Ted -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
