From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] pvresize missing 500GB or more
Date: Wed, 26 Jun 2013 01:32:55 +0200 [thread overview]
Message-ID: <20130625233255.GE25155@soda.linbit> (raw)
In-Reply-To: <"H00000670003132b.1372196759.sx.f1-outsourcing.eu*"@MHS>
On Tue, Jun 25, 2013 at 11:45:59PM +0200, Marc Roos wrote:
>
> We have a reshaped a raid5 array from 11TB to 14TB, on top of this we
> have a drbd device that resized to 14994.5 GB, 14994541563904 bytes,
> but after the pvresize I have
>
>
> pvdisplay
> --- Physical volume ---
> PV Name /dev/drbd21
> VG Name VGstorage21
> PV Size 13.64 TB / not usable 948.00 KB
> Allocatable yes
> PE Size (KByte) 4096
> Total PE 3574977
> Free PE 717377
> Allocated PE 2857600
>
>
> Is it normal to have this much loss?
>
> Thanks in advance,
> Marc
Don't confuse SI units with "binary" units.
pvdisplay TB are actually TiB.
1000 != 1024
1000 * 1000 * 1000 * 1000 != 1024 * 1024 * 1024 * 1024
x**y --> x to the power of y
10**12 / 2**40 = 0.91
2**40 / 10**12 = 1.1
14994541563904 / 2 ** 40
13.64
So yes, in the "terra" range,
it is normal to have about 10 percent "loss"
due to "unit confusion".
more recent LVM tools try to make that clear by using
TB, GB vs TiB, GiB and so on.
you can specify --units in lower case letters for "base 1024",
upper case for "base 1000" units.
pvdisplay --units t
pvdisplay --units T
pvdisplay --units g
pvdisplay --units G
(same goes for all lvm tools)
Lars
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD� and LINBIT� are registered trademarks of LINBIT, Austria.
prev parent reply other threads:[~2013-06-25 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 21:45 [linux-lvm] pvresize missing 500GB or more Marc Roos
2013-06-25 23:32 ` Lars Ellenberg [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=20130625233255.GE25155@soda.linbit \
--to=lars.ellenberg@linbit.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).