From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Richard Ems <richard.ems@cape-horn-eng.com>
Subject: Re: cannot defrag volume, fragmentation factor 21.73%
Date: Mon, 18 Oct 2010 19:58:41 +0200 [thread overview]
Message-ID: <201010181958.42188@zmi.at> (raw)
In-Reply-To: <4CBC4FB7.2040206@cape-horn-eng.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 682 bytes --]
On Montag, 18. Oktober 2010 Richard Ems wrote:
> Attached the gzipped output of 3 runs of xfs_fsr generated with the
> command:
All files reported have "after:1", so where does the fragmentation come
from? Interesting. Maybe a umount;mount helps? Could be the info is just
wrong until a remount?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Radiointerview zum Thema Spam ******
http://www.it-podcast.at/archiv.html#podcast-100716
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- 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:[~2010-10-18 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 12:09 cannot defrag volume, fragmentation factor 21.73% Richard Ems
2010-10-18 12:39 ` Michael Monnerie
2010-10-18 13:46 ` Richard Ems
2010-10-18 17:58 ` Michael Monnerie [this message]
2010-10-18 20:16 ` Stan Hoeppner
2010-10-18 23:10 ` Dave Chinner
2010-10-19 9:37 ` Richard Ems
2010-10-22 10:12 ` Richard Ems
2010-10-22 21:02 ` Michael Monnerie
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=201010181958.42188@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=richard.ems@cape-horn-eng.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox