linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Brown <lvm@davidb.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM on SATA/PATA disks
Date: Mon, 14 May 2007 08:24:05 -0700	[thread overview]
Message-ID: <46487F15.4070108@davidb.org> (raw)
In-Reply-To: <46481E32.4060808@redhat.com>

Bryn M. Reeves wrote:
> David Brown wrote:
> > Of course, any of the re-ordering (SCSI TCQ, or SATA NCQ) requires
> > filesystem and driver support of write barriers for reliability.
> > Write barriers are not implement in DM, hence LVM, so there is a
>
> Only the dm-mpath and dm-snap targets treat barrier bios specially (they
> return EOPNOTSUPP). Other dm targets pass the barriers on to the
> underlying devices unchanged.

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 I'm fairly sure that the write barriers don't work.  This is the
2.6.20 kernel.  XFS is the only filesystem nice enough to warn you
that the result might not be as reliable.

Dave

  reply	other threads:[~2007-05-14 15:24 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 [this message]
2007-05-15 14:35             ` Bryn M. Reeves
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=46487F15.4070108@davidb.org \
    --to=lvm@davidb.org \
    --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).