* Pavel Machek <pavel@xxxxxx> wrote: > Hi! > > > > > As already mentioned, ext3 is just not a good choice for this sort of > > > > thing. Did you have atimes enabled? > > > > > > At least for ext3, more important than atimes is the "data=writeback" > > > setting. Especially since our atime default is sane these days (ie if > > > you don't specify anything, we end up using 'relatime'). > > > > > > If you compile your own kernel, answer "N" to the question > > > > > > Default to 'data=ordered' in ext3? > > > > > > at config time (CONFIG_EXT3_DEFAULTS_TO_ORDERED), or you can make sure > > > "data=writeback" is in the fstab (but I don't think everything honors > > > it for the root filesystem). > > > > Don't forget to mention data=writeback is not the default because if your system > > crashes or you lose power running in this mode it will *CORRUPT YOUR FILESYSTEM* > > and you *WILL LOSE DATA*. Not to mention > > You will lose your data, but the filesystem should still be consistent, right? > Metadata are still journaled. That is data that was freshly touched around the time the system went down, right? I.e. data that was probably half-modified by user-space to begin with. Ingo -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>