public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-xfs@oss.sgi.com
Subject: Re: XFS and write barrier
Date: Sun, 16 Jul 2006 11:53:39 +0200	[thread overview]
Message-ID: <200607161153.40130.Martin@lichtvoll.de> (raw)
In-Reply-To: <20060715192857.GA11034@tuatara.stupidest.org>

Am Samstag 15 Juli 2006 21:28 schrieb Chris Wedgwood:
> On Sat, Jul 15, 2006 at 12:48:56PM +0200, Martin Steigerwald wrote:
> > What are those intermittent IO errors? I googled but did not find a
> > discussion of this change.
>
> write barriers are enabled by default now, they have been for some
> months (since the end of March)

Hallo Chris,

yes, but for 2.6.17 which was still in development. The stable release of 
it appeared kernel.org on 18-Jun-2006 02:10 according to the date in the 
file listing there!

commit 3bbcc8e3976f8bba2fd607c8850d7dfe7e332fda
Author: Nathan Scott <nathans@sgi.com>
Date:   Fri Mar 31 13:04:56 2006 +1000

    [XFS] Reenable write barriers by default.
[...]


They have been in enabled but then disabled again 5 minutes later for 
2.6.16 which should still be widely in use:

commit 4ef19dddbaf2f24e492c18112fd8a04ce116daca
Author: Christoph Hellwig <hch@sgi.com>
Date:   Wed Jan 11 15:27:18 2006 +1100

    [XFS] enable write barriers by default
[...]

commit b04ed21a1fdbfe48ee0738519a4d1af09589dfea
Author: Nathan Scott <nathans@sgi.com>
Date:   Wed Jan 11 15:32:17 2006 +1100

    [XFS] Disable write barriers for now till intermittent IO errors are
    understood.
[...]


Thus for end users this write barrier support by default in XFS is rather 
new!

What I would like to know whether its safe to use write barriers with 
2.6.16 or even 2.6.15 (if it is possible at all) as well (I guess there 
are not many distributions that shipd with 2.6.17 already) or whether one 
might face those "intermittent IO errors" - whatever they are - when 
using them.

If I do not find anything more on this I will recommend 2.6.17 for XFS 
with write barrier usages as I am pretty much convinced that it works 
stable from my own experience. (See my other post.)

Regards,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  reply	other threads:[~2006-07-16  9:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-15 10:48 XFS and write barrier Martin Steigerwald
2006-07-15 19:28 ` Chris Wedgwood
2006-07-16  9:53   ` Martin Steigerwald [this message]
2006-07-17  0:43     ` Chris Wedgwood
2006-07-17  1:24       ` Chris Wedgwood
2006-07-16 17:32 ` Federico Sevilla III
2006-07-18  7:31   ` Nathan Scott
2006-07-18  8:58     ` Neil Brown
2006-07-18 17:04       ` David Chinner
2006-07-18 18:27         ` Martin Steigerwald
2006-07-18 19:21           ` David Chinner
2006-07-20 10:34             ` Martin Steigerwald
2006-07-22  9:31             ` Martin Steigerwald
2006-07-22 10:36               ` Stefan Smietanowski
2006-07-18 23:41         ` Neil Brown

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=200607161153.40130.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-xfs@oss.sgi.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