util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Benno Schulenberg <bensberg@justemail.net>
Cc: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: what precisely is partition_entry_lba?
Date: Wed, 1 Oct 2014 09:59:39 +0200	[thread overview]
Message-ID: <20141001075939.GF26272@x2.net.home> (raw)
In-Reply-To: <1411415045.2373997.170469709.45708397@webmail.messagingengine.com>

On Mon, Sep 22, 2014 at 09:44:05PM +0200, Benno Schulenberg wrote:
> 
> Hi,
> 
> In libfdisk/src/gpt.c the function gpt_list_disklabel() prints
> a GPT header, and one of the things it prints says:
> 
> _("Partitions entries LBA: %ju"), h->partition_entry_lba
> 
> In the struct this variable is described as:
> 
> uint64_t    partition_entry_lba; /* stat LBA of the partition entry array */
> 
> This doesn't make sense to me.  Shouldn't this say something
> like "Starting block of the array of partition entries" instead?

EFI standard:

"The start of the GPT Partition Entry Array is located at the LBA
 indicated by the Partition Entry LBA field."

> All this use of 'lba' is confusing to me, as it stands for
> "logical block addressing", and what seems to be meant
> is simply "logical block" or "logical block number".  No?

Well, "LBA" is usually used as unit (especially in storage slang).
Don't think about it as about abbreviation :-)


IMHO the fdisk message "Partitions entries LBA: %ju" is fine, it's
better to follow commonly terminology.

    Karel


-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2014-10-01  7:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 19:44 what precisely is partition_entry_lba? Benno Schulenberg
2014-10-01  7:59 ` Karel Zak [this message]
2014-10-01 19:34   ` Benno Schulenberg

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=20141001075939.GF26272@x2.net.home \
    --to=kzak@redhat.com \
    --cc=bensberg@justemail.net \
    --cc=util-linux@vger.kernel.org \
    /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).