I tried using it on / and /home when installing Ubuntu 6.10 on taco, this evening.  It installed fine, except for missing xfsprogs, which provide fsck.xfs, by default.

Upon installing a bunch of packages via apt while editing a Perl script at the same time, the machine proceeded to hard lock.  I suspect that there's some hardware glitch in the PC, which is why it's not used all that frequently.  Anyhow, when it rebooted, I first went to my script, to see if vim would be able to recover unsaved changes.  To my dismay, however, the file was full of nulls.  I then tried to resume my package install with "dpkg --configure -a" but soon realized that /var/lib/dpkg/{available,available-old} were also filled with nulls.

I ended up redoing the system with ext3, since I didn't care to spend the time mucking with data recovery.  Was that just some random occurrence, or have other people seen this?

Doesn't give me a great deal of confidence in XFS ...

New comments are currently disabled for this entry.