From: Markus Baertschi <markus@markus.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] VGDA Question
Date: Wed, 14 Sep 2005 22:20:16 +0200 [thread overview]
Message-ID: <43288600.7080501@markus.org> (raw)
In-Reply-To: <20050907144600.42410.qmail@web52915.mail.yahoo.com>
Rik Herrin wrote:
>Hi,
> According to the LVM man page, the VGDA (Volume Group
>Descriptor Area) holds the metadata responsible for
>keeping information about the LVs. However, it is
>contained in the PVs. Why does the VGDA contain both
>LV descriptors and PE descriptors?
>
Because there are LV's with PE's and both types of information must be
stores somewhere.
> Shouldn't it just
>have PE descriptors and leave the LV descriptors to
>the volume group ?
>
The VGDA is where the volume group information is stored. The LV info is
therefore exactly where it belongs.
> Also, when booting, what makes the
>kernel know that there are VGs and LVs?
>
The vgscan command is run during boot (from a rc file) and it detects
the volumegroups and makes them available.
> Does it look
>at the type of the partition and if it detects that
>it's a PV, extract the VGDA to help it build this
>information?
>
Yes
> If this is so, how does it deal with
>entire harddisks. For example, if I run the command:
>pvcreate /dev/sdd
>how would the kernel know that this is a PV?.
>
>
If you use the enire harddisk, then there is no traditional partition
table. In this case the vgscan command looks if the entire disk is a PV.
>Finally, where exactly is the VGDA information held?.
>
At the beginning of the disk/partition you created with pvcreate.
Markus
--
Markus Baertschi Phone: ++41 (21) 807 1677
Bas du Ross� 14b Fax : ++41 (21) 807 1678
CH-1163, Etoy Email: markus@markus.org
Switzerland Homepage: www.markus.org
prev parent reply other threads:[~2005-09-14 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 14:46 [linux-lvm] VGDA Question Rik Herrin
2005-09-08 7:14 ` Luca Berra
2005-09-14 20:20 ` Markus Baertschi [this message]
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=43288600.7080501@markus.org \
--to=markus@markus.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.