Linux LVM users
 help / color / mirror / Atom feed
From: Navindra Umanee <navindra@cs.mcgill.ca>
To: linux-lvm@redhat.com
Subject: [linux-lvm] overallocation of physical volume
Date: Sun, 8 Aug 2004 17:17:59 -0400	[thread overview]
Message-ID: <20040808171759.B6463@cs.mcgill.ca> (raw)

Hi,

  --- Volume group ---
  VG Name               bytepool
  System ID             localhost.localdomain1073237462
  Format                lvm1
  VG Access             read/write
  VG Status             resizable
  MAX LV                256
  Cur LV                6
  Open LV               6
  Max PV                256
  Cur PV                5
  Act PV                5
  VG Size               46.41 GB
  PE Size               32.00 MB
  Total PE              1485
  Alloc PE / Size       1392 / 43.50 GB
  Free  PE / Size       93 / 2.91 GB
  VG UUID               deadbe-efde-adbe-efde-adbe-efde-adbeef


  --- Physical volume ---
  PV Name               /dev/hda7
  VG Name               bytepool
  PV Size               10.00 GB / not usable 60.70 MB
  Allocatable           yes
  PE Size (KByte)       32768
  Total PE              318				 <-------------
  Free PE               4294967262                       <-------------
  Allocated PE          352                              <-------------
  PV UUID               sahdgd-gasj-g21h-xjn4-5jxJ-J45a-asdc3d

  --- Physical volume ---
  PV Name               /dev/hda8
  VG Name               bytepool
  PV Size               10.00 GB / not usable 60.70 MB
  Allocatable           yes
  PE Size (KByte)       32768
  Total PE              318                               <-------------
  Free PE               4294967279                        <-------------
  Allocated PE          335                               <-------------
  PV UUID               sahdgd-gasj-g21h-xjn4-5jxJ-J45a-asdc4d

LVM seems to be claiming to use 352 (or 335 in the second case)
physical extents when there are only 318 total...  Should I be
worried?

Any ideas on how to fix this?

Thanks!
Navin.

                 reply	other threads:[~2004-08-08 21:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040808171759.B6463@cs.mcgill.ca \
    --to=navindra@cs.mcgill.ca \
    --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