public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Andersson <johan@e-626.net>
To: Chris Wedgwood <cw@f00f.org>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_fsr allocation group optimization
Date: Mon, 11 Jun 2007 11:15:56 +0200	[thread overview]
Message-ID: <1181553356.19145.65.camel@gentoo-johan.transmode.se> (raw)
In-Reply-To: <20070611090138.GA28907@tuatara.stupidest.org>

On Mon, 2007-06-11 at 02:01 -0700, Chris Wedgwood wrote:
> using "find .... xfs_fsr" you get temporary files in the same AG as
> the file your are defragmenting, avoiding the spreading out effect,
> but this might not be the least-defragmented file you can get
> 
> what's really needed is an attempt to find space near the original
> file if possible and if not then an option to try harder looking in
> other AGs
This is exactly what the simple but ugly patch I attached achieves by
looking up the filename of the inode it defrags when doing a full file
system defrag. And it works well, except that it spends a lot of time
finding that file name. As I said, a better option would be if you could
tell XFS in what AG you want extents for a newly created file to place
it's extents in. 

/Johan Andersson

  reply	other threads:[~2007-06-11  9:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11  6:51 xfs_fsr allocation group optimization Johan Andersson
2007-06-11  7:35 ` Chris Wedgwood
2007-06-11  8:43   ` Johan Andersson
2007-06-11  9:01     ` Chris Wedgwood
2007-06-11  9:15       ` Johan Andersson [this message]
2007-06-11  9:41         ` Chris Wedgwood
2007-06-11 10:39           ` Johan Andersson
2007-06-11 15:58             ` Chris Wedgwood
2007-06-11 23:07               ` Nathan Scott
2007-06-12  1:38                 ` David Chinner
2007-06-12  1:41         ` David Chinner
2007-06-12  1:44 ` David Chinner
2007-06-15  7:20   ` Timothy Shimmin
2007-06-15  7:24     ` Nathan Scott
2007-06-15  7:40     ` Johan Andersson

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=1181553356.19145.65.camel@gentoo-johan.transmode.se \
    --to=johan@e-626.net \
    --cc=cw@f00f.org \
    --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