From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>,
xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH V2] xfstests 218: very basic defragmentation testing for xfs & ext4
Date: Mon, 10 Aug 2009 10:09:30 -0400 [thread overview]
Message-ID: <20090810140930.GA24174@infradead.org> (raw)
In-Reply-To: <4A7A5CA8.8040702@sandeen.net>
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@lst.de>
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.
prev parent reply other threads:[~2009-08-10 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 20:21 [PATCH] xfstests: very basic defragmentation testing for xfs & ext4 Eric Sandeen
2009-07-15 21:30 ` Andreas Dilger
2009-07-15 21:47 ` Eric Sandeen
2009-07-18 14:31 ` Christoph Hellwig
2009-07-18 16:30 ` Eric Sandeen
2009-08-06 4:31 ` [PATCH V2] xfstests 218: " Eric Sandeen
2009-08-10 14:09 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090810140930.GA24174@infradead.org \
--to=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).