From: Eric Sandeen <sandeen@sandeen.net>
To: LinuxRaid <linux-raid@vger.kernel.org>, xfs-oss <xfs@oss.sgi.com>
Subject: md raid1 passes barriers, but xfs doesn't use them?
Date: Mon, 23 Jun 2008 21:23:10 -0500 [thread overview]
Message-ID: <48605A8E.9070903@sandeen.net> (raw)
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:
if (mp->m_ddev_targp->bt_bdev->bd_disk->queue->ordered ==
QUEUE_ORDERED_NONE) {
xfs_fs_cmn_err(CE_NOTE, mp,
"Disabling barriers, not supported by the underlying
device");
mp->m_flags &= ~XFS_MOUNT_BARRIER;
return;
}
winds up with XFS disabling barriers on these devices. However, if this
is simply commented out, XFS happily tests barriers, finds that they
work, leaves them turned on and all subsequent barrier writes to the
device succeed.
Perhaps what we have here is a failure to communicate? :)
I'm not sure; *should* XFS be looking for a QUEUE_ORDERED tag? Should
MD be setting one? Maybe there should be a QUEUE_ORDERED_PASSTHRU flag?
Or should XFS just stick with the test write and ignore the flag? I'm
not sure of the queue->ordered flag details, but it seems that XFS & md
raid1 both try hard to keep barriers in force, and there's a disconnect
here somewhere.
Thanks,
-Eric
next reply other threads:[~2008-06-24 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 2:23 Eric Sandeen [this message]
2008-06-24 22:57 ` md raid1 passes barriers, but xfs doesn't use them? 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=48605A8E.9070903@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-raid@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).