On Wed, Jun 08, 2011 at 03:47:33PM +0200, Michael Monnerie wrote:
> The difference could be that your filesystem is very much aged, and the
> free space clustered around to new files get heavily fragmented. Did you
> run xfs_defrag often? How full is your filesystem?
Doesn't seem to be the case:
pyre:~# xfs_db -c frag -r /dev/vg0/shared
actual 61132, ideal 60937, fragmentation factor 0.32%
(thats the old/slow filesystem)
I re-created the test filesystem to be the same size (20gb) as the
original, and copied all the same files to it, so both are now 80% full.
pyre:~# lvremove /dev/vg0/newshared
Do you really want to remove active logical volume newshared? [y/n]: y
Logical volume "newshared" successfully removed
pyre:~# lvcreate -L 20G -n newshared vg0
Logical volume "newshared" created
I also tried to replicate the same sunit/swidth options, but mkfs.xfs is
too smart for its own good and ignored my settings:
pyre:~# mkfs.xfs -f -d sunit=0,swidth=0 -l sunit=0 /dev/vg0/newshared
meta-data=/dev/vg0/newshared isize=256 agcount=16, agsize=327664
= sectsz=512 attr=2, projid32bit=0
data = bsize=4096 blocks=5242624, imaxpct=25
= sunit=16 swidth=32 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal log bsize=4096 blocks=2560, version=2
= sectsz=512 sunit=16 blks,
realtime =none extsz=4096 blocks=0, rtextents=0
pyre:~# mount /dev/vg0/newshared /mnt/tmp
pyre:~# cp -a /shared/* /mnt/tmp/
pyre:/# cd /mnt/tmp
pyre:/mnt/tmp# sync;sleep 15s;time ionice -c1 tar -zxf
> Also the log has sunit=0 against 16, maybe there's the diff.
> Are you on a newer kernel that supports delaylog? Then try that.
Yes, it could be that the mount options only set sunit/swidth for the
data section and not the journal, so metadata operations are much
slower. I am not able to test as mkfs.xfs ignores my command line
options and sets the values even if I tell it they should be 0..