All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Ems <richard.ems@cape-horn-eng.com>
To: xfs@oss.sgi.com
Subject: cannot defrag volume, fragmentation factor 21.73%
Date: Mon, 18 Oct 2010 14:09:52 +0200	[thread overview]
Message-ID: <4CBC3910.70806@cape-horn-eng.com> (raw)

Hi all,

this is on openSUSE 11.3.

# uname -a
Linux fs1 2.6.34.7-0.3-default #1 SMP 2010-09-20 15:27:38 +0200 x86_64 
x86_64 x86_64 GNU/Linux

# echo frag | xfs_db -r /dev/disk/by-label/data1
xfs_db> actual 6451844, ideal 5050129, fragmentation factor 21.73%

# xfs_db -V
xfs_db version 3.1.2

# xfs_fsr -V
xfs_fsr version 3.1.2

# df -h /dev/sdb1
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1              17T   13T  4.3T  75% /data_1


The volume is new, 12TB were rsync'ed from another volume, some new 
files came after the sync.

I ran several times xfs_fsr, but the 21.73% factor stays there.
There where some busy or modified files on which I started xfs_fsr later 
again, but this ones where small files and the 21.73% is still there.

Any ideas?

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

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2010-10-18 12:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18 12:09 Richard Ems [this message]
2010-10-18 12:39 ` cannot defrag volume, fragmentation factor 21.73% Michael Monnerie
2010-10-18 13:46   ` Richard Ems
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=4CBC3910.70806@cape-horn-eng.com \
    --to=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 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.