On Wed, Aug 05, 2009 at 11:31:36PM -0500, Eric Sandeen wrote: > Test a few very basic defragmentation scenarios. > > This test creates some files, runs defrag on them, > and compares the before/after fragmentation as well > as file md5sums and timestamps. > > The test currently expects to find e4defrag in > /usr/bin > > It should be relatively easy to add more interestingly > fragmented files to the tests, as well as to test > that memory-mapped files aren't touched, etc - > but this gives us a framework. > > V2: remount before checking file contents, and create > common.defrag. The patch loks good to me, Reviewed-by: Christoph Hellwig <hch@xxxxxx> Unfortunately it still fails on my Debian testing system with: QA output created by 218 zero-length file: -Before: 0 -After: 0 +Before: 1 +After: 1 Sparse file (no blocks): -Before: 0 -After: 0 +Before: 1 +After: 1 But that's due to a bug in filefrag that I have already reported to the Debian BTS. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
