From: Richard Ems <richard.ems@cape-horn-eng.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: cannot defrag volume, fragmentation factor 21.73%
Date: Mon, 18 Oct 2010 15:46:31 +0200 [thread overview]
Message-ID: <4CBC4FB7.2040206@cape-horn-eng.com> (raw)
In-Reply-To: <201010181439.48143@zmi.at>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
On 10/18/2010 02:39 PM, Michael Monnerie wrote:
> On Montag, 18. Oktober 2010 Richard Ems wrote:
>> I ran several times xfs_fsr, but the 21.73% factor stays there.
>
> Possibly you have some very big files which cannot be defraged? What
> output does xfs_fsr -v give?
>
>
There are no very big files, surely some with a couple of GBs but not
more. All files are defragmented.
Attached the gzipped output of 3 runs of xfs_fsr generated with the command:
{ set -x ; for i in 1 2 3 ; do date ; echo frag | xfs_db -r
/dev/disk/by-label/data1 ; date ; xfs_fsr -v /data_1/ ; date ; echo frag
| xfs_db -r /dev/disk/by-label/data1 ; date ; done ; set +x ;} >
~/logs/defrag/data1/xfs_fsr-HOME-2010.10.18-1.log 2>&1 &
Thanks, Richard
--
Richard Ems mail: Richard.Ems@Cape-Horn-Eng.com
Cape Horn Engineering S.L.
C/ Dr. J.J. Dómine 1, 5º piso
46011 Valencia
Tel : +34 96 3242923 / Fax 924
http://www.cape-horn-eng.com
[-- Attachment #2: xfs_fsr-HOME-2010.10.18-1.log.gz --]
[-- Type: application/x-gzip, Size: 218367 bytes --]
[-- Attachment #3: 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 13:45 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 [this message]
2010-10-18 17:58 ` Michael Monnerie
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=4CBC4FB7.2040206@cape-horn-eng.com \
--to=richard.ems@cape-horn-eng.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 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.