From: Mike Snitzer <snitzer@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Data alignment
Date: Fri, 19 Mar 2010 18:21:56 -0400 [thread overview]
Message-ID: <20100319222156.GE7345@redhat.com> (raw)
In-Reply-To: <4BA3EC26.7000302@cfl.rr.com>
On Fri, Mar 19 2010 at 5:27pm -0400,
Phillip Susi <psusi@cfl.rr.com> wrote:
> On 3/19/2010 3:25 PM, Mike Snitzer wrote:
> > Any reason why you'd like to use DOS partitioning (first primary
> > partition starting at 63rd sector)?
>
> Convention. I am looking into using GPT instead though.
>
> > Anyway, if you have a recent kernel (e.g. 2.6.33) you'll be in good
> > shape regardless. If you create a partition on the device (using DOS
> > partitions) the kernel _should_ be aware of where the partition starts
> > and tell you how far you'd have to shift the start of your LVM2 PV data
> > area to get it perfectly aligned relative to the underlying physical
> > block size. Check for example:
> > # cat /sys/block/sda/sda1/alignment_offset
> >
> > But if your device is using 512b physical_sector_size you'll just have a
> > 0 for alignment_offset. Check physical_block_size with:
> > # cat /sys/block/sda/queue/physical_block_size
>
> 0 alignment, physical block size 512.
>
> > Also verify that your SSD device is naturally aligned (aka
> > alignment_offset=0); I'd wager it is naturally aligned:
> > # cat /sys/block/sda/alignment_offset
>
> Kernel thinks so, and based on performance tests it appears so.
>
> > All said, even if you have an older kernel, to manually get what you
> > want (shift start to account for DOS partition at 63rd sector, align PV
> > pe_start on a 512K boundary), please try:
> > # pvcreate --dataalignmentoffset 512b --dataalignment 512K ...
>
> Won't that just add one sector to the start, placing it at sector 1025?
> How does an alignment offset of 1 sector account for the partition
> starting on sector 63?
The --dataalignmentoffset acts as padding. I was focused on getting you
to a power of 2 start (sector 64). Then from there --dataalignment
governs the start boundary for the PV data area.
So you're right, 64*512b + 512K isn't a multiple of 512K :)
This will get you what you want:
# pvcreate --dataalignmentoffset 512b --dataalignment 480K /dev/sda1
# pvs --units s -o+pe_start /dev/sda1
PV VG Fmt Attr PSize PFree 1st PE
/dev/sda1 lvm2 a- 20971457S 20971457S 961S
961*512b + 63*512b = 512K
next prev parent reply other threads:[~2010-03-19 22:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 18:13 [linux-lvm] Data alignment Phillip Susi
2010-03-19 18:36 ` Eugene Vilensky
2010-03-19 18:54 ` Phillip Susi
2010-03-19 19:54 ` Ray Morris
2010-03-19 21:20 ` Phillip Susi
2010-03-20 7:32 ` Luca Berra
2010-03-19 19:25 ` Mike Snitzer
2010-03-19 21:27 ` Phillip Susi
2010-03-19 22:21 ` Mike Snitzer [this message]
2010-03-19 23:11 ` Mike Snitzer
2010-03-25 12:54 ` [linux-lvm] Called while suspended Fredrik Skog
2010-03-20 23:02 ` [linux-lvm] Data alignment Stuart D. Gathman
-- strict thread matches above, loose matches on Subject: below --
2013-02-12 14:58 Phillip Susi
2013-02-12 15:10 ` Mike Snitzer
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=20100319222156.GE7345@redhat.com \
--to=snitzer@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).