From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Kenneth Emerson <kenneth.emerson@gmail.com>,
Stan Hoeppner <stan@hardwarefreak.com>
Subject: Re: Defragging XFS File Systems
Date: Thu, 9 Jun 2011 07:49:36 +0200 [thread overview]
Message-ID: <201106090749.37745@zmi.at> (raw)
In-Reply-To: <4DEFE2E6.9010206@hardwarefreak.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 781 bytes --]
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.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// Haus zu verkaufen: http://zmi.at/langegg/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-06-09 5:49 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 [this message]
2011-06-09 8:13 ` Stan Hoeppner
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=201106090749.37745@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=kenneth.emerson@gmail.com \
--cc=stan@hardwarefreak.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.