From: Karel Zak <kzak@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Advanced Format disks mixed with regular disks?
Date: Tue, 15 Mar 2011 09:02:43 +0100 [thread overview]
Message-ID: <20110315080243.GA14681@nb.net.home> (raw)
In-Reply-To: <20110314200057.GB18904@redhat.com>
On Mon, Mar 14, 2011 at 04:00:57PM -0400, Mike Snitzer wrote:
> On Mon, Mar 14 2011 at 3:13pm -0400,
> Ron Johnson <ron.l.johnson@cox.net> wrote:
>
> > On 03/14/2011 12:17 PM, Mike Snitzer wrote:
> > >On Mon, Mar 14 2011 at 12:47pm -0400,
> > >Ron Johnson<ron.l.johnson@cox.net> wrote:
> > >
> > >>Hi,
> > >>
> > >>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
> > >
> >
> > Does this mean that util-linux v2.17.1 fdisk correctly handle AF
> > disks? (Note that I will *not* be booting off an AF device.)
ideally util-linux >= 2.17.2 (e.g. RHEL6)
> >
> > ftp://ftp.kernel.org/pub/linux/utils/util-linux/v2.17/v2.17.1-ReleaseNotes
> >
> > fdisk:
> > - cleanup alignment, default to 1MiB offset [Karel Zak]
> > - don't check alignment_offset against geometry [Karel Zak]
> > - fallback for topology values [Karel Zak]
> > - fix ALIGN_UP [Karel Zak]
> > - fix check_alignment() [Karel Zak]
> > - fix default first sector [Karel Zak]
> > - use "optimal I/O size" in warnings [Karel Zak]
> > - use 1MiB offset and grain always when possible [Karel Zak]
> > - use more elegant way to count and check alignment [Karel Zak]
> > - use optimal_io_size [Karel Zak]
>
> Given that changelog, yes.
Yes, it works. Note that you have to disable (-c -u) DOS compatible
mode. The mode is disabled by default in Fedora, but enabled in RHEL6.
Some hints:
http://karelzak.blogspot.com/2010/05/4096-byte-sector-hard-drives.html
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2011-03-15 8:02 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
2011-03-14 19:13 ` Ron Johnson
2011-03-14 20:00 ` Mike Snitzer
2011-03-15 8:02 ` Karel Zak [this message]
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=20110315080243.GA14681@nb.net.home \
--to=kzak@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=snitzer@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).