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: Sat, 12 May 2007 19:06:30 -0700	[thread overview]
Message-ID: <464672A6.3000408@davidb.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0705122130070.27083-100000@bmsred.bmsi.com>

Stuart D. Gathman wrote:

>> How does SATA fit in with all of this?  Is it basically the same
>> limitations on the bus as IDE/PATA, so that you'd really not want to put
>> more than 1 device per bus?
>
> SATA mandates at most 1 disk per channel, making the issue moot.  It is
> still true that there is only one active disk on a bus.  But then there
> is only one disk on a bus.

Newer SATA drives, with proper newer controllers and proper device
driver support will support NCQ (native command queueing), which
allows the drive to re-order requests.  It appears that the Linux ACHI
and Nvidia SATA drivers support this capability in recent kernels.

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
reliability risk in going with this kind of solution.  Depending on
the filesystem this can result in power failures resulting in files
having inconsistent data.

Dave

  reply	other threads:[~2007-05-13  2:06 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 [this message]
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
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=464672A6.3000408@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).