linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "David F." <df7729@gmail.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Trying to understand format of LVM2 - Question on Extent Size
Date: Wed, 25 Jul 2018 21:25:04 -0700	[thread overview]
Message-ID: <CAGRSmLuo1ivu5eskvPMvNzmwOWFtUrnOEKUKHaTtjk7ynwc+BA@mail.gmail.com> (raw)
In-Reply-To: <CAGRSmLtZ9N7f6y+GpiZ-mVxW_-qh9h6LgTY=q+P39z4vDcK44w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]

Never mind, the answer is the extent_size is the number of sectors (or
perhaps it's the number of 512 byte blocks, I'll have to test on 4K sector
drives).     So in this case 4M and 4M*3840 is the 16G (not 16M which was
the 3840*4096).

On Wed, Jul 25, 2018 at 5:37 PM, David F. <df7729@gmail.com> wrote:

> I created a test lvm on a 32G UFD with two logical volumes, 15G and 14G.
> I then looked at the on disk data and most makes since except the
> extent_count vs extent_size.   In this case the extent_size is 8192, and it
> says the extent sizes are 3840 and 3584, but that * 8192 is double its
> actual size.   * 4096 then it is the size.  So how does that work.  TIA!!
> Here's the sample:
>
> test_lvm {
> id = "xhewgS-UxVF-4qC5-MGXp-ErfX-6SNl-UkCdgz"
> seqno = 3
> format = "lvm2"
> status = ["RESIZEABLE", "READ", "WRITE"]
> flags = []
> extent_size = 8192
> max_lv = 0
> max_pv = 0
> metadata_copies = 0
>
> physical_volumes {
>
> pv0 {
> id = "XhEzob-g2D5-YcGp-zfz9-39R7-HII6-SITlH9"
> device = "/dev/sdc"
>
> status = ["ALLOCATABLE"]
> flags = []
> dev_size = 62531584
> pe_start = 2048
> pe_count = 7633
> }
> }
>
> logical_volumes {
>
> lvm_logvol {
> id = "IIKGTj-2eYn-5iTk-7KZd-ZMzS-aqYT-kwNgko"
> status = ["READ", "WRITE", "VISIBLE"]
> flags = []
> creation_time = 1532609310
> creation_host = "localhost.localdomain"
> segment_count = 1
>
> segment1 {
> start_extent = 0
> extent_count = 3840
>
> type = "striped"
> stripe_count = 1
>
> stripes = [
> "pv0", 0
> ]
> }
> }
>
> lvm_logvol2 {
> id = "dC9wIq-kJ3I-ixLV-A2f9-889Y-qpUr-DdfciL"
> status = ["READ", "WRITE", "VISIBLE"]
> flags = []
> creation_time = 1532609325
> creation_host = "localhost.localdomain"
> segment_count = 1
>
> segment1 {
> start_extent = 0
> extent_count = 3584
>
> type = "striped"
> stripe_count = 1
>
> stripes = [
> "pv0", 3840
> ]
> }
> }
> }
>
> }
> # Generated by LVM2 version 2.02.168(2) (2016-11-30): Thu Jul 26 08:48:45
> 2018
>
> contents = "Text Format Volume Group"
> version = 1
>
> description = ""
>
> creation_host = "localhost.localdomain"    # Linux localhost.localdomain
> 4.11.8-300.fc26.x86_64 #1 SMP Thu Jun 29 20:09:48 UTC 2017 x86_64
> creation_time = 1532609325    # Thu Jul 26 08:48:45 2018
>
>

[-- Attachment #2: Type: text/html, Size: 2964 bytes --]

  reply	other threads:[~2018-07-26  4:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26  0:37 [linux-lvm] Trying to understand format of LVM2 - Question on Extent Size David F.
2018-07-26  4:25 ` David F. [this message]
2018-07-26  8:58   ` Zdenek Kabelac

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=CAGRSmLuo1ivu5eskvPMvNzmwOWFtUrnOEKUKHaTtjk7ynwc+BA@mail.gmail.com \
    --to=df7729@gmail.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).