Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
and yes, I've seen KDE broken after an unplanned shutdown on XFS but there was never any confusion or doubt on my mind that it was a KDE problem)
Posted Mar 17, 2009 20:15 UTC (Tue) by quotemstr (subscriber, #45331)
Posted Mar 18, 2009 1:08 UTC (Wed) by bojan (subscriber, #14302)
1. It was written by SGI, so most distros don't have internal resources to support it. So, they ship other FSes as default.
2. Other FSes were historically the default, so upgrading to XFS is not that straightforward.
3. Some people unjustly accused this FS of loosing data, so it is taking a long time for the FS to get its reputation back. Even if all those that did the accusing published public retractions of their unfounded accusations, it would take a long time.
Posted Mar 18, 2009 11:15 UTC (Wed) by arekm (subscriber, #4846)
Otherwise I'm very happy with xfs and I'll continue to use it.
Posted Mar 17, 2009 20:26 UTC (Tue) by sbergman27 (guest, #10767)
Users who get hoist with that particular petard have clearly done it to themselves. "XFS does it too" is really academic.
Posted Mar 17, 2009 20:47 UTC (Tue) by gmaxwell (subscriber, #30048)
I don't disagree with the position that the end result is a "linux (distribution) problem" to the end user. But the problem is not the filesystem or the kernel. The problem is the dependence on zillions of tiny dot files (or a registry, *cough*, gconf) which absolutely can't be corrupt. Even if EXT4 provides the EXT3 behaviour there will always be opportunities for these files to become corrupted (software/hardware failure, cosmic ray, etc) and that the failure frequently results in an inability to even login is simply unacceptable. Quite arguably the file system which demonstrates its corner case behaviour more frequently is preferable since it means that developers will be more aware and more likely to address these situations.
Posted Mar 17, 2009 22:27 UTC (Tue) by sbergman27 (guest, #10767)
Posted Mar 18, 2009 19:58 UTC (Wed) by chad.netzer (✭ supporter ✭, #4257)
Posted Mar 27, 2009 7:20 UTC (Fri) by Duncan (guest, #6647)
IOW, AFAICT, the bad reiserfs rep originates in the pre-2.6.6 era, quite
some time ago now, and it's actually a quite stable and mature fs now.
That has certainly been my experience, both bad back then, with corrupt or
zeroed files at boot after a crash pre-data=ordered, and impressively
stable, now and for several years, post-data=ordered.
Again, if you have references otherwise, I'm willing to be corrected, but
I believe reiserfs is actually reasonably similar to ext3 in this regard,
and has been for some years, now.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds