[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090831132139.GA5425@infradead.org>
Date: Mon, 31 Aug 2009 09:21:39 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Mark Lord <lkml@....ca>
Cc: Christoph Hellwig <hch@...radead.org>,
Ric Wheeler <rwheeler@...hat.com>,
Michael Tokarev <mjt@....msk.ru>, david@...g.hm,
Pavel Machek <pavel@....cz>, Theodore Tso <tytso@....edu>,
NeilBrown <neilb@...e.de>, Rob Landley <rob@...dley.net>,
Florian Weimer <fweimer@....de>,
Goswin von Brederlow <goswin-v-b@....de>,
kernel list <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...l.org>, mtk.manpages@...il.com,
rdunlap@...otime.net, linux-doc@...r.kernel.org,
linux-ext4@...r.kernel.org, corbet@....net
Subject: Re: raid is dangerous but that's secret (was Re: [patch] ext2/3:
document conditions when reliable operation is possible)
On Mon, Aug 31, 2009 at 09:19:58AM -0400, Mark Lord wrote:
>> In my opinion even that is too weak. We know how to control the cache
>> settings on all common disks (that is scsi and ata), so we should always
>> disable the write cache unless we know that the whole stack (filesystem,
>> raid, volume managers) supports barriers. And even then we should make
>> sure the filesystems does actually use barriers everywhere that's needed
>> which failed at for years.
> ..
>
> That stack does not know that my MD device has full battery backup,
> so it bloody well better NOT prevent me from enabling the write caches.
No one is going to prevent you from doing it. That question is one of
sane defaults. And always safe, but slower if you have advanced
equipment is a much better default than usafe by default on most of
the install base.
--
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