lkml.org 
[lkml]   [2010]   [Nov]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.6.36 io bring the system to its knees

* Pavel Machek <pavel@ucw.cz> 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


\
 
 \ /
  Last update: 2010-11-10 15:31    [W:1.095 / U:0.480 seconds]
©2003-2014 Jasper Spaans. Advertise on this site