From: Gionatan Danti <g.danti@assyoma.it>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: "Yu, Mingli" <Mingli.Yu@windriver.com>
Subject: Re: [linux-lvm] The size specified by "lvcreate -L" is not accurate
Date: Thu, 02 Sep 2021 15:24:00 +0200 [thread overview]
Message-ID: <ba1b736723487985ec076d499d89313b@assyoma.it> (raw)
In-Reply-To: <PH0PR11MB501412E2C1081FA98208E545F1CE9@PH0PR11MB5014.namprd11.prod.outlook.com>
Il 2021-09-02 05:26 Yu, Mingli ha scritto:
> Per
> https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/doc/RelNotes/v1.46.4.txt
> [1], after e2fsprogs upgrades to 1.46.4, the defaults for mke2fs now
> call for 256 byte inodes for all file systems (with the exception of
> file systems for the GNU Hurd, which only supports 128 byte inodes)
> and use "lvcreate -L 50 -n lv_test1 vg_test && mke2fs
> /dev/vg_test/lv_test1" and then continue to check the partiontion as
> below.(use lvm2 2.03.11 for the test)
> # df -h | grep dev/mapper/vg_test-lv_test1
>
> /dev/mapper/vg_test-lv_test1 48M 14K 46M 1% /mnt/lv-test
>
> Though claim 50M as above, but it turns out to be only 48M.
I think that allocation are done in multiple of physical extent size
which, by default, is at 4 MB.
50 is not a multiple of 4 while 48 is, so "lvcreate" probably rounded
down the required size.
Using one or more "-v" should bring progressively more details.
Regards.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
_______________________________________________
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:[~2021-09-02 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 3:26 [linux-lvm] The size specified by "lvcreate -L" is not accurate Yu, Mingli
2021-09-02 13:24 ` Gionatan Danti [this message]
2021-09-02 14:23 ` 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=ba1b736723487985ec076d499d89313b@assyoma.it \
--to=g.danti@assyoma.it \
--cc=Mingli.Yu@windriver.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).