Xfs is still faster but ext4 is catching up on large file creation
tytso.livejournal.com
tytso.livejournal.com
The notion that XFS is unreliable probably stems from the way such lost buffered data has historically been handled. Because XFS allocates the space ahead of actually writing the data, files with unwritten data at a reset could have visible zero-filled blocks after recovery whereas ext3 would simply truncate them. In both cases the data was lost.
Since a while back, unwritten extents like these are detected and trimmed back, so now XFS behaves more like most other filesystems. There are still more buffered writes floating about, of course, so the same precautions are still required.
A more important aspect is how well the filesystem recovers from having the plug pulled, and here they all do well. Once written to disk, data is stable in all of the mentioned filesystems. This is in contrast to non-journalling ones where an unclean shutdown can render the on-disk data inconsistent and difficult to recover.
I am really interested to know. Right now I am running EXT4 on an SSD in my notebook. It performs well. Sometimes, after a suspend , I get a load of EXT4 error messages which are stalling the whole notebook. Hard resseting it, makes the error disappear. Up to now, no data loss.But anyway, this makes me a nervous and I am not sure if it is due to Kernel, SSD, Ext4 or the combination of all/any of them. I guess XFS is way out of my use point, but anyway, an option is an option.
ext4: what errors are you getting? I've not seen any so far.
EDIT: Ok I see what's going on. paines is having problems with EXT4 and suspends. I wasn't talking about that. I was responding to nodata's XFS losing data fud.