Messages in this thread | | | Date | Tue, 13 Jul 2004 23:27:50 -0700 | From | Roy Butler <> | Subject | Re: kconfig's file handling (was: XFS: how to NOT null files on fsck?) |
| |
On Tue, Jul 13, 2004 at 02:31:43PM +0200, Waldo Bastian wrote: > > The sentiment among filesystem developers seem to be that they don't care if > they trash files as long as the filesystem itself remains in a consistent > state. This kind of dataloss is the result of that attitude, either go > complain with them if it bothers you, or use a filesystem that does it right. >
Exactly. Don't blame KDE. Using XFS is equivalent to using non-battery-backed NVRAM on an external disk array. Great if performance is _the_ metric and lost results can easily be regenerated (like in frame rendering). By example, if you create a file, write to it, and then delete it fast enough, it will never hit the disk under XFS.
Roy Butler - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |