Red Hat Bugzilla – Bug 238386
Inconsistent logical volume sizes between RHEL5 and Fedora-devel
Last modified: 2007-11-30 17:12:03 EST
Description of problem:
In installation stage, the logical volume sizes show in RHEL 5 and Fedora Test4
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RHEL 5 with LVM logical volumes.
2. When edit logical volumes inside a Volume group, note down the total space
(ex. Total Space: 152352.00 MB)
3. After RHEL 5 installed, install Fedora Test 4
3. In the partition layout screen, click on one of the logical volume, then
4. Compare the total space from RHEL 5 (shown as Used space here), and total
space in Fedora-test 4 (ex. 152320.00 MB). The free space is -32.00 MB in this
In Edit LVM Volume Group: VolGroup00
Used Space: 152352.00 MB (100.0%)
Free Space: -32.00 MB (-0.0%)
Total Space: 152320.00 MB
Used Space: 152320.00 MB (100.0%)
Free Space: 0.00 MB (0.0%)
Total Space: 152320.00 MB
Went through this briefly last week - not sure if this ls an LVM2 or installer
bug (looked a bit through anaconda code last week and noticed a few fixes that
might be related but wasn't sure). Anaconda people - does this look like a
possible installer bug? Leaving as lvm for now.
Those numbers are from anaconda. Run the F7 lvm2 tools directly and see what
values they give you.
(In reply to comment #3)
> Those numbers are from anaconda. Run the F7 lvm2 tools directly and see what
> values they give you.
I don't see any obvious incorrect output from the scan
commands or xxdisplay commands on my F7 system. The scan
output is not to verbose so I included it here.
[root@raven ~]# uname -a
Linux raven.themaw.net 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007
x86_64 x86_64 x86_64 GNU/Linux
Perhaps it's arch specific or Anaconda.
[root@raven ~]# vgscan
Reading all physical volumes. This may take a while...
Found volume group "mvg" using metadata type lvm2
Found volume group "VolGroup02" using metadata type lvm2
Found volume group "VolGroup00" using metadata type lvm2
[root@raven ~]# pvscan
PV /dev/sdb5 VG mvg lvm2 [22.89 GB / 18.89 GB free]
PV /dev/sdb6 VG mvg lvm2 [22.89 GB / 22.89 GB free]
PV /dev/sdb7 VG mvg lvm2 [22.18 GB / 22.18 GB free]
PV /dev/sdb1 VG VolGroup02 lvm2 [42.92 GB / 0 free]
PV /dev/sdb2 VG VolGroup02 lvm2 [38.15 GB / 0 free]
PV /dev/sda3 VG VolGroup00 lvm2 [74.41 GB / 43.47 GB free]
Total: 6 [223.44 GB] / in use: 6 [223.44 GB] / in no VG: 0 [0 ]
[root@raven ~]# lvscan
ACTIVE '/dev/mvg/tlv' [4.00 GB] inherit
ACTIVE '/dev/VolGroup02/LogVol00' [81.07 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol00' [12.00 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol01' [1.94 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol02' [5.00 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol03' [12.00 GB] inherit
I used to have this problem in April 2007. However, the problem dispeared in
early May (I forget the exact date). Maybe there are some patch which fix this
Closing per comment #5.