Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] different outputs in LVM tools (bug?)
Date: Wed, 25 Jul 2001 11:01:50 +0200	[thread overview]
Message-ID: <20010725110150.B24685@sistina.com> (raw)
In-Reply-To: <3B5E7271.887177CC@atix.de>; from julien@atix.de on Wed, Jul 25, 2001 at 09:17:05AM +0200

On Wed, Jul 25, 2001 at 09:17:05AM +0200, Julien Baboud wrote:
> hi,
> 
>  I'm using the 0.9.1 beta 7 version, and I have encountered a problem
> (but perhaps it is not) with the LVM tools :
>  when I use the 'vgdisplay' command I obtain this :
> 
> --- Volume group ---
> VG Name               vg1
> VG Access             read/write
> VG Status             available/resizable
> VG #                  0
> MAX LV                256
> Cur LV                4
> Open LV               0
> MAX LV Size           255.99 GB
> Max PV                256
> Cur PV                2
> Act PV                2
> VG Size               1000 MB
> PE Size               4 MB
> Total PE              250
> Alloc PE / Size       100 / 400 MB
> Free  PE / Size       150 / 600 MB
> VG UUID               qnJMzM-yuCq-N59y-cTey-kayU-9Wo3-hGILhU
> 
> 
> and with the 'vgdisplay -c' command, the output is :
> 
> vg1:3:5:0:256:4:0:268427264:256:2:2:1024000:8192:250:100:150:qnJMzM-yuCq-N59y-cTey-kayU-9Wo3-hGILhU
>                                             ----
> 
> The difference is in the 'PE Size' field : in the first we have 4 MB and
> in the second 8192 (ie : 8 MB)
> Is this a known bug or is there any explanation ?

Julien,

internally LVM uses units of 512 byte -> 8192 * 512 byte == 4 MB.

> 
> 
> Julien,
> 4 Atix
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2001-07-25  9:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-25  7:17 [linux-lvm] different outputs in LVM tools (bug?) Julien Baboud
2001-07-25  9:01 ` Heinz J . Mauelshagen [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=20010725110150.B24685@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.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