linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] label sector and non 512 byte sectors
Date: Thu, 3 Jan 2013 18:02:54 +0000	[thread overview]
Message-ID: <20130103180254.GC19165@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <50DB10B4.1000505@gmail.com>

On Wed, Dec 26, 2012 at 09:59:00AM -0500, Phillip Susi wrote:
> The man page for pvcreate states that the label goes in the second
> sector.  That means it SHOULD be at an offset of 4096 bytes when using
> 4096 byte sectors, but apparently it is still at an offset of 512 bytes.
>  Bug?
 
We define a sector at 512 bytes. Always.

Some documentation could be improved to make that clearer.

Alasdair

  reply	other threads:[~2013-01-03 18:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26 14:59 [linux-lvm] label sector and non 512 byte sectors Phillip Susi
2013-01-03 18:02 ` Alasdair G Kergon [this message]
2013-01-03 19:13   ` Stuart D Gathman

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=20130103180254.GC19165@agk-dp.fab.redhat.com \
    --to=agk@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).