I am happily using xfs for /var, /usr and /, and I am very pleased with the read speed. I've just recommended xfs to a friend, and he complained about the speed of rm. I did a test on my box, and in
mount -o logbsize=262144 <dev> <mtpt> BTW, noatime implies nodiratime - you don't ned to specify both. At 1.1T, you probably want to use inode64 for /var. The different allocation strategy of inode32
I've added it to my mount options, also tried logbufs=8 (but that didn't make much difference). Thanks for the suggestions, the time for rm has improved a bit, but is still slower than reiserfs: time
Others' suggestions stand, but I have found the best way to speed up a journalled filesystem (of any kind) is with an external journal on a separate controller channel. If your XFS journal is interna
Hi, I am happily using xfs for /var, /usr and /, and I am very pleased with the read speed. I've just recommended xfs to a friend, and he complained about the speed of rm. I did a test on my box, and
mount -o logbsize=262144 <dev> <mtpt> BTW, noatime implies nodiratime - you don't ned to specify both. At 1.1T, you probably want to use inode64 for /var. The different allocation strategy of inode32
I've added it to my mount options, also tried logbufs=8 (but that didn't make much difference). Thanks for the suggestions, the time for rm has improved a bit, but is still slower than reiserfs: time
Others' suggestions stand, but I have found the best way to speed up a journalled filesystem (of any kind) is with an external journal on a separate controller channel. If your XFS journal is interna
Buy more disks. ;) XFS is not really optimised for single disk, metadata intensive, small file workloads. It scales by being able to keep lots of disks busy at the same time. Those algorithms don't m