On 12 Oct 2016, at 16:54, Dave Chinner wrote: >> Like me, generic/285 seems to have gotten this wrong too, but > > The test isn't wrong - it's just a demonstration of the fact we > can't easily cater for every different allocation strategy that > filesystems and storage uses to optimise IO patterns and pervent > fragmentation. Regarding generic/285 -- I'd like to have it work for NFS. Maybe using SEEK_DATA to discover an appropriate allocation size for filesystems exported by NFS could work by writing to increasing offsets until a seek for data from the beginning of the file reveals the second allocation. That seems to work for xfs, ext4, btrfs, and tmpfs exports. I'll send a patch with that to fstests. Ben -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
