public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: AndCycle <andcycle@andcycle.idv.tw>
To: xfs@oss.sgi.com
Subject: xfs_fsr defrag top 10% that have the largest number of extents??
Date: Wed, 31 Mar 2010 06:28:14 +0800	[thread overview]
Message-ID: <4BB27AFE.2030205@andcycle.idv.tw> (raw)

my xfs_fsr version is xfsdump_2.2.48-1,

there is a description in xfs_fsr man said
"
When invoked with no arguments xfs_fsr reorganizes all regular files in 
all mounted filesystems.
(...)
Each pass goes through and selects files that have the largest number of 
extents.  It attempts to defragment the top 10% of these files on each pass.
"
but xfs_fsr -d telling me it defrags in inode ascending order,

http://pastebin.com/h0RyZkwA

is this a normal behavior?



_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2010-03-30 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 22:28 AndCycle [this message]
2010-03-31  4:00 ` xfs_fsr defrag top 10% that have the largest number of extents?? Dave Chinner

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=4BB27AFE.2030205@andcycle.idv.tw \
    --to=andcycle@andcycle.idv.tw \
    --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