From: Stan Hoeppner <stan@hardwarefreak.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: Kenneth Emerson <kenneth.emerson@gmail.com>, xfs@oss.sgi.com
Subject: Re: Defragging XFS File Systems
Date: Thu, 09 Jun 2011 03:13:32 -0500 [thread overview]
Message-ID: <4DF080AC.2090507@hardwarefreak.com> (raw)
In-Reply-To: <201106090749.37745@zmi.at>
On 6/9/2011 12:49 AM, Michael Monnerie wrote:
> On Mittwoch, 8. Juni 2011 Kenneth wrote:
>>> After that, I will make
>>> a cron job to run on a regular basis to keep the volume from
>>> getting so fragmented again.
>
> How will you do that? Running xfs_fsr on a regular basis is *not*
> recommended, as it will age your filesystem and defrag free space. In
> the beginning, and as long as your filesystem is maybe 50% full it will
> be fine, but there's a point where it starts to get worse - much worse.
> Just run a recent kernel, it has all the naughty stuff to help keep the
> performance high.
When *is* running xfs_fsr recommended?
I scheduled it twice a week some time ago due to a filesystem containing
active mbox files. I did so because they became so heavily fragmented
in short order, especially those swallowing copious amounts of list
mail. Before cron'ing xfs_fsr I was seeing mbox files with over 1000
fragmented extents, and increasing MUA latency as the files became more
fragmented. The filesystem is currently 90% free.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-06-09 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 3:52 Defragging XFS File Systems Kenneth Emerson
2011-06-07 5:48 ` Stewart Smith
2011-06-07 12:05 ` Stan Hoeppner
[not found] ` <BANLkTikBSL8-eTAbF7a94ckLuZNyWCM=Eg@mail.gmail.com>
2011-06-08 21:00 ` Stan Hoeppner
2011-06-09 5:49 ` Michael Monnerie
2011-06-09 8:13 ` Stan Hoeppner [this message]
2011-06-09 10:12 ` Michael Monnerie
2011-06-09 18:24 ` Stan Hoeppner
2011-06-10 17:56 ` Dave Chinner
2011-06-11 1:12 ` Stan Hoeppner
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=4DF080AC.2090507@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=kenneth.emerson@gmail.com \
--cc=michael.monnerie@is.it-management.at \
--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