From: Roger James <roger@beardandsandals.co.uk>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Where are the data blocks of an LV?
Date: Tue, 26 Jul 2022 09:58:38 +0100 [thread overview]
Message-ID: <18239bac630.27a5.d4b3b9aee17a85f6bc878c68b3925db6@beardandsandals.co.uk> (raw)
In-Reply-To: <CAFsGsxLOyawZH7xxgfLNkh=VftBNAaDStE0XQgQTGf9NmyZ+ZQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 754 bytes --]
See https://talk.manageiq.org/t/lvm-internals-structures-disk-layout/1328
On 26 July 2022 09:16:31 Marcin Owsiany <marcin@owsiany.pl> wrote:
> Hello,
>
> I know that it is possible to find where a given logical volume's extents
> start on a PVs thanks to the information printed by lvdisplay --maps.
>
> I was also able to experimentally establish that the actual data of an LV
> starts one megabyte after that location. Is that offset documented
> anywhere, or can I somehow discover it at runtime for a given LV?
>
> regards,
> Marcin
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://listman.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
[-- Attachment #1.2: Type: text/html, Size: 1976 bytes --]
[-- Attachment #2: Type: text/plain, Size: 202 bytes --]
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2022-07-27 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 17:30 [linux-lvm] Where are the data blocks of an LV? Marcin Owsiany
2022-07-26 8:58 ` Roger James [this message]
2022-07-26 18:22 ` 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=18239bac630.27a5.d4b3b9aee17a85f6bc878c68b3925db6@beardandsandals.co.uk \
--to=roger@beardandsandals.co.uk \
--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).