Messages in this thread | | | Date | Tue, 13 Jul 2004 17:02:54 -0400 | From | Theodore Ts'o <> | 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. >
Ext3 with ordered writes (the default) gets this right.
Unfortunately, cheating can give you better benchmark resuls, and some people seem to care more about better benchmark results than silly things like user's files not getting wiped. For many workloads, especially for user desktops, the disk bandwidth isn't saturated, and given that most writes are asynchronous in nature, a faster write benchmark for a particular filesystem or filesystme mode may not translate into a user-visible difference. So focusing on improved write speeds at the cost of data robustness can very often be false economy.
- Ted - 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/
| |