From: "Bryn M. Reeves" <breeves@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM on SATA/PATA disks
Date: Tue, 15 May 2007 15:35:27 +0100 [thread overview]
Message-ID: <4649C52F.9080000@redhat.com> (raw)
In-Reply-To: <46487F15.4070108@davidb.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David Brown wrote:
> A simple lvm volume, mounted with XFS gives the following kernel
> message:
>
> Filesystem "dm-11": Disabling barriers, not supported by the underlying
> device
> XFS mounting filesystem dm-11
So it does. I don't use XFS on my boxes & hadn't noticed this before.
Turns out that xfs is checking barrier capabilities using queue->ordered
in the device struct. If it has QUEUE_ORDERED_NONE, barriers are
disabled (fs/xfs/linux-2.6/xfs_super.c).
I'll look into why this is the case as given this check there shouldn't
be any need for snap & mpath to check for barrier bios themselves.
The patches that introduced those checks were submitted after problems
were seen with barriers on these target types, so something was clearly
submitting them at some stage.
Kind regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGScUv6YSQoMYUY94RAh3sAKCpcTdyvLKpwni1VYssyo2cORBG6ACbBrbl
xlJIlDXDdZGNAX5Tmjbt7RI=
=yaL7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-05-15 14:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 21:42 [linux-lvm] LVM on SATA/PATA disks Bertrand Renuart
2007-05-13 1:12 ` Stuart D. Gathman
2007-05-13 1:23 ` Brian J. Murrell
2007-05-13 1:34 ` Stuart D. Gathman
2007-05-13 2:06 ` David Brown
2007-05-13 16:46 ` Les Mikesell
2007-05-13 17:24 ` Stuart D. Gathman
2007-05-14 8:38 ` Bryn M. Reeves
2007-05-14 8:30 ` Bryn M. Reeves
2007-05-14 15:24 ` David Brown
2007-05-15 14:35 ` Bryn M. Reeves [this message]
2007-05-13 20:25 ` Bertrand Renuart
2007-05-14 14:53 ` Stuart D. Gathman
2007-05-14 14:59 ` Daniel Davidson
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=4649C52F.9080000@redhat.com \
--to=breeves@redhat.com \
--cc=linux-lvm@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).