Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756179Ab0KJOUr (ORCPT ); Wed, 10 Nov 2010 09:20:47 -0500 Received: from ksp.mff.cuni.cz ([195.113.26.206]:33390 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755816Ab0KJOUq (ORCPT ); Wed, 10 Nov 2010 09:20:46 -0500 Date: Wed, 10 Nov 2010 15:20:37 +0100 From: Pavel Machek To: Dave Chinner Cc: Linus Torvalds , Jens Axboe , dave b , Sanjoy Mahajan , Jesper Juhl , Chris Mason , Ingo Molnar , Pekka Enberg , Aidar Kultayev , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton , Peter Zijlstra , Nick Piggin , Arjan van de Ven , Thomas Gleixner , "Ted Ts'o" , Corrado Zoccolo , Shaohua Li , Steven Barrett Subject: Re: 2.6.36 io bring the system to its knees Message-ID: <20101110142037.GA1447@ucw.cz> References: <20101105014334.GF13830@dastard> <4CD696B4.6070002@kernel.dk> <20101110013255.GR2715@dastard> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101110013255.GR2715@dastard> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1525 Lines: 38 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. > the significant security issues (e.g stale data exposure) that also > occur even if the filesystem is not corrupted by the crash. IOWs, I agree on security issues. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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/