| |||||||||||||
Maybe btrfs has no fsck,Maybe btrfs has no fsck,Posted Jun 18, 2009 11:37 UTC (Thu) by viiru (subscriber, #53129)In reply to: Maybe btrfs has no fsck, by drag Parent article: What ever happened to chunkfs?
> One of the strengths of Ext3 over XFS and Reiserfs is it's fsck. The
> journalling features of XFS and Reiserfs only protect the filesystem (aka > metadata) from corruption, it does not help protect your actual data or > detect problems with your data. For that you need to do fsck for Ext3.
Well. Actually XFS has both the ability to recover from an unclean shutdown without fsck, and a full featured repair tool. Don't be confused by the fact that the fsck.xfs-tool is essentially /bin/true. The repair tool exists, but it goes by the name of xfs_repair.
I've been using XFS on Linux in production on most of my machines for the past six years or so, and have needed to run xfs_repair twice. Haven't lost any files, either.
The "it eats your filez"-reputation of XFS has been greatly exaggerated.
(Log in to post comments)
If only Posted Jun 18, 2009 12:20 UTC (Thu) by khim (subscriber, #9252) [Link] The "it eats your filez"-reputation of XFS has been greatly exaggerated. I've had rock solid way to reproduce this effect: run bittorrent client on 100% full filesystem. Sure, this is not nice thing to do for a filesystem (and currently btrfs does not handle this case all that well), but stuff happens. If I can not trust my filesystem in such conditions how can I trust it at all? It looks like XFS problems are in the past but trust is easy to lose, hard to resurrect - now I'm firmly in ext3 camp.
|
|||||||||||||