public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Just Marc <marc@corky.net>
Cc: Barry Naujok <bnaujok@sgi.com>, xfs@oss.sgi.com
Subject: Re: xfs_fsr, performance related tweaks
Date: Fri, 29 Jun 2007 17:08:14 +1000	[thread overview]
Message-ID: <20070629070814.GR31489@sgi.com> (raw)
In-Reply-To: <4684A98B.1030000@corky.net>

On Fri, Jun 29, 2007 at 07:41:15AM +0100, Just Marc wrote:
> Barry Naujok wrote:
> >You can use the xfs_io chattr command to mark known files as
> >nodefrag. Using the chattr -R option can be used to recurse
> >directories.
> 
> That's right but I can't do this on a filesystem that's just been 
> defragged say a minute ago, and in the mean time 20 new files got added 
> (I don't know what these files are... ).

So walk the filesystem with a script that queries the number of
extents in each file, and if they have a single extent then
run the xfs_io on them.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-06-29  7:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28 12:47 xfs_fsr, performance related tweaks Just Marc
2007-06-28 20:38 ` Eric Sandeen
2007-06-29  0:52   ` Andi Kleen
2007-06-29  6:21   ` Just Marc
2007-06-29  6:41     ` Barry Naujok
2007-06-29  6:41       ` Just Marc
2007-06-29  7:08         ` David Chinner [this message]
2007-06-29  7:16           ` Just Marc
2007-06-29  7:33             ` Nathan Scott
2007-06-29  7:41             ` David Chinner
2007-06-29  7:39               ` Just Marc
2007-06-30 17:17               ` Eric Sandeen
2007-07-01 22:43                 ` David Chinner
  -- strict thread matches above, loose matches on Subject: below --
2007-06-28 12:47 Just Marc
2007-06-29  0:12 ` Nathan Scott
2007-06-29  6:31   ` Just Marc
2007-06-29  8:13     ` Andi Kleen
2007-06-29  8:23       ` Just Marc
2007-06-29  8:58         ` Andi Kleen

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=20070629070814.GR31489@sgi.com \
    --to=dgc@sgi.com \
    --cc=bnaujok@sgi.com \
    --cc=marc@corky.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