Yah for production go with a kernel as close to stock as posible. Avoid
anything by redhat in the 2.4.20 series, and you should be fine. In other
words go get a fresh treee, patch in ONLY the XFS stuff. Don't put in low
latency/preeempt patches, they still screw everything up. And just stay
away from RedHate kernels.
--On Wednesday, August 06, 2003 9:03 AM +0100 Gordon Henderson
I am running a few production servers with XFS now, but I'm a little
concerned... (as I'm seeing some problems)
Anyway, I'm using the -ac4 patches to 2.4.21 with the 1.2 release of the
xfsprogs and with overnight cron "stuff", (eg. amanda) I get a bunch of
processes hanging in the "D" state. Eg. xfsdump. This doesn't inspire
confidence. Right now I'm seeing:
1149 ? D 2:20 xfsdump -F -J -l 1 - /dev/md4
9275 ? D 2:02 du -k
10103 ? D 2:26 /usr/bin/find / ( -fstype NFS -o -fstype nfs -o
21671 ? D 1:28 /usr/bin/rsync -a --delete -H -x .
/mounts/local0.yesterday/ 13976 ? D 1:16 du -k
14776 ? D 1:59 /usr/bin/find / ( -fstype NFS -o -fstype nfs -o
which isn't good. A few days ago I had a bunch of nfsd's stuck in D state
too which required a reboot - which in a busy working environment isn't a
good thing )-:
Is XFS really ready for production?
I'm faced with migrating this box back to ext2 and hoping we never get a
powerfail (it's on a big UPS, but there is a limit!) as it has 2 x 160GB
partitions which I can live without the fsck time... (and this is just the
start, I have another half terabyte server with XFS too - I shudder to
think of the fsck time on that!)
Any clues other than "get the latest CVS patches"?