From: Tomasz Chmielewski <mangoo@wpkg.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] fdisk and lvs size differences
Date: Wed, 09 Jan 2008 15:51:02 +0100 [thread overview]
Message-ID: <4784DF56.6090903@wpkg.org> (raw)
In-Reply-To: <4784CF70.3000307@redhat.com>
Bryn M. Reeves schrieb:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Tomasz Chmielewski wrote:
>> Let's say I have a 500GB logical volume:
>>
>> # lvs | grep san2_data
>> san2_data san1 -wi-a- 500.00G
>>
>>
>> fdisk will report a bigger number:
>>
>> # fdisk -l /dev/san1/san2_data
>>
>> Disk /dev/san1/san2_data: 536.8 GB, 536870912000 bytes
>
> It's just units; the G in lvm's output signifies powers-of-two units,
> wheras the GB reported by fdisk is in powers-of-ten (SI units).
>
> See the lvm man pages for a description of the units supported (lower
> case are SI, upper case are powers-of-two).
What lvm manual exactly? I didn't find anything about upper/lower case
units supported in "man lvcreate" or "man lvm". In fact, it didn't make
a difference here whether I used "g" or "G".
Of course, I could calculate it manually, but I'd rather have it done
automatically.
# lvcreate -L500g -n san2_data san1
Logical volume "san2_data" created
# fdisk -l /dev/san1/san2_data
Disk /dev/san1/san2_data: 536.8 GB, 536870912000 bytes
# lvcreate -L500G -n san2_data san1
Logical volume "san2_data" created
# fdisk -l /dev/san1/san2_data
Disk /dev/san1/san2_data: 536.8 GB, 536870912000 bytes
# lvm version
LVM version: 2.02.07 (2006-07-17)
Library version: 1.02.08 (2006-07-17)
Driver version: 4.11.0
This is on Debian Etch.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2008-01-09 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 13:36 [linux-lvm] fdisk and lvs size differences Tomasz Chmielewski
2008-01-09 13:43 ` Bryn M. Reeves
2008-01-09 14:51 ` Tomasz Chmielewski [this message]
2008-01-09 16:13 ` Bryn M. Reeves
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=4784DF56.6090903@wpkg.org \
--to=mangoo@wpkg.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.