linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Eric A" <erpo41@gmail.com>
To: "Eric Sandeen" <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Fwd: barriers off by default?
Date: Mon, 12 May 2008 13:11:51 -0600	[thread overview]
Message-ID: <72c5d9a0805121211l50e1b136xf33e0b3b7fda103c@mail.gmail.com> (raw)
In-Reply-To: <482893C2.7000709@redhat.com>

On Mon, May 12, 2008 at 1:00 PM, Eric Sandeen <sandeen@redhat.com> wrote:
> Eric A wrote:
>  >  Documentation/block/barrier.txt
>  >
>  >  There's a section that starts:
>  >
>  >  "* Error handling.  Currently, block layer will report error to upper
>  >  layer if any of requests in an ordered sequence fails.  Unfortunately,
>  >  this doesn't seem to be enough. "
>
>
>
> And ends:
>
>  "As the probability of this happening is very low and the drive should
>  be faulty, implementing the fix is probably an overkill.  But, still,
>  it's there."
>
>  I'm not sure it's an argument for disabling barriers in general.   :)

I agree; it's just something that's been bugging me since I started
searching for a solution for zfs-fuse. Maybe performance is the
reason? Flushing the write cache is kind of slow.

Cheers,
Eric

  reply	other threads:[~2008-05-12 19:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12 15:56 barriers off by default? Eric Sandeen
2008-05-12 17:30 ` Eric A
2008-05-12 17:53   ` Eric Sandeen
     [not found]     ` <72c5d9a0805121150j58482bc6qd57a87089ce4414e@mail.gmail.com>
2008-05-12 18:51       ` Fwd: " Eric A
2008-05-12 19:00         ` Eric Sandeen
2008-05-12 19:11           ` Eric A [this message]
2008-05-12 19:15             ` Eric Sandeen
2008-05-15 14:43 ` Jan Kara
2008-05-15 16:00   ` Eric Sandeen
2008-05-15 16:21     ` Andreas Dilger
2008-05-15 18:34       ` Eric Sandeen
2008-05-15 20:44   ` Eric Sandeen
2008-05-16  0:21     ` Jan Kara
2008-05-16  0:58       ` Eric Sandeen
2008-05-17 17:38         ` Theodore Tso
2008-05-17 19:02           ` Eric Sandeen

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=72c5d9a0805121211l50e1b136xf33e0b3b7fda103c@mail.gmail.com \
    --to=erpo41@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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).