From: Roel van Meer <rolek@bokxing.nl>
To: xfs@oss.sgi.com
Subject: Re: XFS defragmentation issue
Date: Mon, 13 Sep 2010 10:05:25 +0200 [thread overview]
Message-ID: <cone.1284365125.256876.62928.1001@bork.lsof.org> (raw)
In-Reply-To: 4C8BDAC8.8010203@hardwarefreak.com
Stan Hoeppner writes:
> Out of curiosity, who here schedules automatic xfs_fsr runs, and with
> what frequency? Currently I just run it manually now and then when
> performance starts to seem sluggish.
I run it daily during the week, at a time when load is practically nil, on
two boxes with 24TB storage each, divided into six parts of about 4GB. A
10-pass xfs_fsr run usually completes in under one hour, except on monday,
when it takes three to four hours.
I don't have any stats on the net effect, though.
Regards,
roel
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-09-13 8:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 14:41 XFS defragmentation issue John Lister
2010-09-10 19:00 ` Stan Hoeppner
2010-09-11 6:55 ` John Lister
2010-09-11 8:23 ` Dave Chinner
2010-09-11 8:25 ` John Lister
2010-09-11 19:38 ` Stan Hoeppner
2010-09-11 19:57 ` Iustin Pop
2010-09-12 1:01 ` Dave Chinner
2010-09-12 8:43 ` Emmanuel Florac
2010-09-12 9:45 ` Stan Hoeppner
2010-09-13 8:05 ` Roel van Meer [this message]
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=cone.1284365125.256876.62928.1001@bork.lsof.org \
--to=rolek@bokxing.nl \
--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