From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-xfs@oss.sgi.com
Subject: Re: md raid1 passes barriers, but xfs doesn't use them?
Date: Tue, 24 Jun 2008 11:31:11 +0200 [thread overview]
Message-ID: <200806241131.12112.Martin@lichtvoll.de> (raw)
In-Reply-To: <48605A8E.9070903@sandeen.net>
Hi Eric!
Am Dienstag 24 Juni 2008 schrieb Eric Sandeen:
> So md raid1 is happy to pass down any barrier writes that it sees, but
> this bit in xfs_mountfs_check_barriers() at mount time:
Interesting. Since when?
On my last test also ext3 disabled barries over device mapper /
reiserfs[1]. well but I used it with LVM, maybe its different with RAID
1. I thought this to be a generic device mapper issue.
Did you test with ext3 too?
[1] http://bugzilla.kernel.org/show_bug.cgi?id=9554
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2008-06-24 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 2:23 md raid1 passes barriers, but xfs doesn't use them? Eric Sandeen
2008-06-24 9:31 ` Martin Steigerwald [this message]
2008-06-24 13:34 ` Eric Sandeen
2008-06-24 14:25 ` Martin Steigerwald
2008-06-24 22:57 ` Dave Chinner
2008-06-25 1:49 ` 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=200806241131.12112.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