[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikNPEcwWjEQuC-_=9yH5DCCiwUAY265ggeygcSQ@mail.gmail.com>
Date: Sun, 7 Nov 2010 07:50:13 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Jens Axboe <axboe@...nel.dk>
Cc: dave b <db.pub.mail@...il.com>, Sanjoy Mahajan <sanjoy@...n.edu>,
Dave Chinner <david@...morbit.com>,
Jesper Juhl <jj@...osbits.net>,
Chris Mason <chris.mason@...cle.com>,
Ingo Molnar <mingo@...e.hu>, Pekka Enberg <penberg@...nel.org>,
Aidar Kultayev <the.aidar@...il.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Nick Piggin <npiggin@...e.de>,
Arjan van de Ven <arjan@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
"Ted Ts'o" <tytso@....edu>, Corrado Zoccolo <czoccolo@...il.com>,
Shaohua Li <shaohua.li@...el.com>,
Steven Barrett <damentz@...il.com>
Subject: Re: 2.6.36 io bring the system to its knees
On Sun, Nov 7, 2010 at 4:08 AM, Jens Axboe <axboe@...nel.dk> wrote:
>
> 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).
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists