From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests 042: point xfs_fsr right at the fragmented file
Date: Fri, 8 May 2009 02:26:58 -0400 [thread overview]
Message-ID: <20090508062658.GA1689@infradead.org> (raw)
In-Reply-To: <4A0386FD.7000108@sandeen.net>
On Thu, May 07, 2009 at 08:12:29PM -0500, Eric Sandeen wrote:
> Somehow 042 as it stands isn't actually defragging the fragmented
> file we created (see 042.full post-run)
>
> Probably need to look into that as well, but for now this should
> make the call to fsr actually _do_ something.
>
> This has let 2 fsr bugs slip through qa in the past few months. :(
Looks good. Can you open a bugzilla for the problem of fsr not actually
finding the fragmented file so that we don't forget about that one?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-05-08 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 1:12 [PATCH] xfstests 042: point xfs_fsr right at the fragmented file Eric Sandeen
2009-05-08 6:26 ` Christoph Hellwig [this message]
2009-05-08 12:43 ` Eric Sandeen
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=20090508062658.GA1689@infradead.org \
--to=hch@infradead.org \
--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