From: Bruno Wolff III <bruno@wolff.to>
To: Mark Lewis <mark.lewis@mir3.com>
Cc: Brian Wipf <brian@clickspace.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: File Systems Compared
Date: Mon, 11 Dec 2006 11:54:11 -0600
Message-ID: <20061211175411.GA3236@wolff.to> (raw)
In-Reply-To: <1165424114.9734.298.camel@archimedes>
References: <BEB285F8-0BD2-4524-BD46-B1D35E7EFBEB@clickspace.com>
<82bqmh3rfc.fsf@mid.bfk.de>
<1165424114.9734.298.camel@archimedes>
On Wed, Dec 06, 2006 at 08:55:14 -0800,
Mark Lewis <mark.lewis@mir3.com> wrote:
> > Anyone run their RAIDs with disk caches enabled, or is this akin to
> > having fsync off?
>
> Disk write caches are basically always akin to having fsync off. The
> only time a write-cache is (more or less) safe to enable is when it is
> backed by a battery or in some other way made non-volatile.
>
> So a RAID controller with a battery-backed write cache can enable its
> own write cache, but can't safely enable the write-caches on the disk
> drives it manages.
This appears to be changing under Linux. Recent kernels have write barriers
implemented using cache flush commands (which some drives ignore, so you
need to be careful). In very recent kernels, software raid using raid 1
will also handle write barriers. To get this feature, you are supposed to
mount ext3 file systems with the barrier=1 option. For other file systems,
the parameter may need to be different.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: bruno@wolff.to, mark.lewis@mir3.com, brian@clickspace.com
Subject: Re: File Systems Compared
In-Reply-To: <20061211175411.GA3236@wolff.to>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox