linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Ron Johnson <ron.l.johnson@cox.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Advanced Format disks mixed with regular disks?
Date: Mon, 14 Mar 2011 13:09:43 -0500	[thread overview]
Message-ID: <4D7E59E7.3090203@cox.net> (raw)
In-Reply-To: <20110314180250.GA18622@redhat.com>

On 03/14/2011 01:02 PM, Mike Snitzer wrote:
> On Mon, Mar 14 2011 at  1:32pm -0400,
> Les Mikesell<lesmikesell@gmail.com>  wrote:
>
>> On 3/14/2011 12:17 PM, Mike Snitzer wrote:
>>>
>>>> Is there any concern with mixing 4KB-sector drives with 512-byte
>>>> sector drives in the same LV?
>>>
>>> Both LVM2 and Device Mapper have been updated to accommodate stacking
>>> such a mix of drives.
>>>
>>> See this for a bit more detail:
>>> http://people.redhat.com/msnitzer/docs/io-limits.txt
>>>
>>> Particularly, the "Stacking I/O Limits" section.
>>>
>>> The concern raised for partial (4k) writes to the 512b drive was
>>> discussed a bit more here: http://lkml.org/lkml/2010/2/22/295
>>
>> Are there any version-level hints about when/where these changes
>> appear and come together in the real world (i.e. distributions like
>> RHEL, debian, Ubuntu)?
>
> For the kernel, the bulk of associated infrastructure (ata, scsi, block,
> dm, md, etc) went in 2.6.31, 2.6.32 saw some improvements, and 2.6.33
> and 2.6.34 saw a few bug fixes.
>
> v2.6.32.11 saw a backport of the 2.6.33 and 2.6.34 bug fixes via commit
> 9b2ff97
>
> RHEL6 has all this.  I cannot speak for debian and/or Ubuntu.
>
> As for LVM2, you'd want>= 2.02.62.
>

Thanks...

$ cat /etc/debian_version
wheezy/sid

$ /sbin/lvm version
   LVM version:     2.02.84(2) (2011-02-09)
   Library version: 1.02.63 (2011-02-09)

$ uname -r
2.6.37-2-amd64

-- 
I prefer banana-flavored energy bars made from tofu.

  reply	other threads:[~2011-03-14 18:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 16:47 [linux-lvm] Advanced Format disks mixed with regular disks? Ron Johnson
2011-03-14 17:17 ` Mike Snitzer
2011-03-14 17:32   ` Les Mikesell
2011-03-14 18:02     ` Mike Snitzer
2011-03-14 18:09       ` Ron Johnson [this message]
2011-03-14 19:13   ` Ron Johnson
2011-03-14 20:00     ` Mike Snitzer
2011-03-15  8:02       ` Karel Zak
2011-03-15 14:24         ` Stuart D. Gathman
2011-03-15 17:36           ` Stuart D. Gathman
2011-03-15  0:15     ` John Drescher
2011-03-16 20:45   ` Phillip Susi
2011-03-16 22:55     ` Mike Snitzer
2011-03-16 23:11       ` Les Mikesell
2011-03-17  0:02         ` Mike Snitzer
2011-03-17  0:18           ` Mike Snitzer
2011-03-17  0:12       ` Phillip Susi
2011-03-17  0:39         ` Martin K. Petersen
2011-03-17 14:21           ` hansbkk
2011-03-17 23:47           ` Ron Johnson
2011-03-22 10:23             ` Karel Zak
2011-03-22 16:51               ` Les Mikesell

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=4D7E59E7.3090203@cox.net \
    --to=ron.l.johnson@cox.net \
    --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).