LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ric Wheeler <ric@emc.com>
To: device-mapper development <dm-devel@redhat.com>,
Michael Tokarev <mjt@tls.msk.ru>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org
Subject: Re: [dm-devel] Re: [PATCH] Implement barrier support for single device DM devices
Date: Mon, 18 Feb 2008 07:48:07 -0500 [thread overview]
Message-ID: <47B97E87.6040209@emc.com> (raw)
In-Reply-To: <20080215141229.GB1788@agk.fab.redhat.com>
Alasdair G Kergon wrote:
> On Fri, Feb 15, 2008 at 03:20:10PM +0100, Andi Kleen wrote:
>> On Fri, Feb 15, 2008 at 04:07:54PM +0300, Michael Tokarev wrote:
>>> I wonder if it's worth the effort to try to implement this.
>
> My personal view (which seems to be in the minority) is that it's a
> waste of our development time *except* in the (rare?) cases similar to
> the ones Andi is talking about.
Using working barriers is important for normal users when you really
care about data loss and have normal drives in a box. We do power fail
testing on boxes (with reiserfs and ext3) and can definitely see a lot
of file system corruption eliminated over power failures when barriers
are enabled properly.
It is not unreasonable for some machines to disable barriers to get a
performance boost, but I would not do that when you are storing things
you really need back.
Of course, you don't need barriers when you either disable the write
cache on the drives or use a battery backed RAID array which gives you a
write cache that will survive power outages...
ric
next prev parent reply other threads:[~2008-02-18 12:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 12:08 [PATCH] Implement barrier support for single device DM devices Andi Kleen
2008-02-15 12:20 ` Alasdair G Kergon
2008-02-15 13:07 ` Michael Tokarev
2008-02-15 14:20 ` Andi Kleen
2008-02-15 14:12 ` [dm-devel] " Alasdair G Kergon
2008-02-15 15:34 ` Andi Kleen
2008-02-15 15:31 ` Alan Cox
2008-02-18 12:48 ` Ric Wheeler [this message]
2008-02-18 13:24 ` Michael Tokarev
2008-02-18 13:52 ` Ric Wheeler
2008-02-19 2:45 ` Alasdair G Kergon
2008-05-16 19:55 ` Mike Snitzer
2008-05-16 21:48 ` Andi Kleen
2008-02-18 22:16 ` David Chinner
2008-02-19 2:56 ` Alasdair G Kergon
2008-02-19 5:36 ` David Chinner
2008-02-19 9:43 ` Andi Kleen
2008-02-19 7:19 ` Jeremy Higdon
2008-02-19 7:58 ` Michael Tokarev
2008-02-20 13:38 ` Ric Wheeler
2008-02-21 3:29 ` Neil Brown
2008-02-21 3:39 ` Neil Brown
2008-02-17 23:31 ` David Chinner
2008-02-19 2:39 ` Alasdair G Kergon
2008-02-19 11:12 ` David Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47B97E87.6040209@emc.com \
--to=ric@emc.com \
--cc=andi@firstfloor.org \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).