From: Dave Wysochanski <dwysocha@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] On-disk and LVM internal metadata representation
Date: Mon, 05 Mar 2007 11:12:23 -0500 [thread overview]
Message-ID: <1173111143.4432.29.camel@linux-cxyg.rtp.netapp.com> (raw)
In-Reply-To: <45EC51C0.669D.00E9.0@novell.com>
On Mon, 2007-03-05 at 04:54 -0700, Nallammai S wrote:
> Hi,
>
> Whats the difference between on-disk metadata and LVM internal representation? How does LVM map between these two representations?
>
> Thanks in advance.
>
> Nallammai.S
>
It is different for LVM1 vs LVM2.
LVM2
- text-based on-disk metadata
- format-specific code in lib/format_text
LVM1
- binary on-disk metadata
- format-specific code in lib/format1
If you read the import*.[ch] and export*.[ch] files in the format
specific directories you will get an understanding of the mapping. I
also found following the label_read() function to be helpful.
prev parent reply other threads:[~2007-03-05 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 11:54 [linux-lvm] On-disk and LVM internal metadata representation Nallammai S
2007-03-05 16:12 ` Dave Wysochanski [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=1173111143.4432.29.camel@linux-cxyg.rtp.netapp.com \
--to=dwysocha@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).