From: Nathan Scott <nathans@sgi.com>
To: xfs@oss.sgi.com
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: XFS and write barrier
Date: Tue, 18 Jul 2006 17:31:22 +1000 [thread overview]
Message-ID: <20060718173122.B1914501@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20060716173238.GD3417@free.net.ph>; from jijo@free.net.ph on Mon, Jul 17, 2006 at 01:32:38AM +0800
On Mon, Jul 17, 2006 at 01:32:38AM +0800, Federico Sevilla III wrote:
> On Sat, Jul 15, 2006 at 12:48:56PM +0200, Martin Steigerwald wrote:
> > I am currently gathering information to write an article about journal
> > filesystems with emphasis on write barrier functionality, how it
> > works, why journalling filesystems need write barrier and the current
> > implementation of write barrier support for different filesystems.
>
> Cool! Would you by any chance have information on the interaction
> between journal filesystems with write barrier functionality, and
> software RAID (md)? Based on my experience with 2.6.17, XFS detects that
> the underlying software RAID 1 device does not support barriers and
> therefore disables that functionality.
Noone here seems to know, maybe Neil &| the other folks on linux-raid
can help us out with details on status of MD and write barriers?
cheers.
--
Nathan
next prev parent reply other threads:[~2006-07-18 7:32 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
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 [this message]
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=20060718173122.B1914501@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=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