On Mon, Oct 18, 2010 at 02:09:52PM +0200, Richard Ems wrote:
> Hi all,
> this is on openSUSE 11.3.
> # uname -a
> Linux fs1 22.214.171.124-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
Understand your numbers. What frag reports is how many extents there
are vs a perfect layout. It does not tell you how badly fragmented
your filesystem is. Extent-based filesystems can have
"fragmentation" like you see reported above, but not suffer at all
because the extents are large enough not to affect IO throughput.
e.g. If I have a 100GB file in 100x1GB extents, frag would report an
ideal of 17 extents and measure 100. That would give a frag factor
of 83%. Now, is that filesystem fragmented? Theoretically yes.
Why? Because extents of 1GB are more than large enough for any IO to
that file reach full throughput. Therefore, while the file layout is
not perfect, the "fragmentation" has no impact on performance and
therefore the filesystem should not be considered fragmented.
So, for 13TB of data, having 20% of your files with two extents
rather than one is not a problem unless that causes you application
measurable performance issues...
IOWs, trying to reduce fragmentation without understanding what the
numbers tell you about the layout of your filesystem can be counter
productive. Especially as running xfs_fsr when you don't really need
to can have other side-effects that affect the long-term aging
characteristics of the filesystem (e.g. causing preamture free space