-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Justin Dugger wrote:
Similarly anecdotal, a dormmate of mine ran XFS for a while. Then one day he spilled some water near the extension cord and guitar amp he'd plugged into his UPS. In a frantic move he unplugged the wrong cable during an emerge and discovered a number of binaries full of ^@ (null).
My XFS experience is similar...nasty problems with data corruption on unclean shutdowns with linux.
I now run JFS, which has worked almost flawlessly across many sudden unexpected power outages. I chose JFS over EXT3 several years ago mostly due to it's resizing features and some filesystem features.
Resizing a JFS partition is as simple as extending the logical volume it's on top of, and issuing a 'mount -o remount,resize <mountpoint>'. Takes all of a couple seconds. Resizing ext involves marching through the filesystem and mucking around with numerous bits of metadata, which takes forever and seems more prone to catastrophic failure.
I also occasionally tend to run out of inodes on ext file-systems, and I have found no easy way to increase them once the filesystem is online.
I'm hoping ext4 will address both issues, because while I love JFS, it's not getting a lot of current development, and the ext filesystems are far and away the most used/tested of the linux filesystems.
...oh the "almost" in almost flawlessly, above: I have several times run a JFS filesystem completely out of disk space. Once, this caused the filesystem to become corrupt and unmountable. A simple offline fsck fixed the problem, however, and all was well (once I acquired some additional storage, that is! :).
- -- Charles Steinkuehler [email protected]