Bug#686096: again on another machine
I've finally observed something like this again, may or may not be related
On this second machine, there was an existing VG and existing NTFS
partitions (Windows and Lenovo recovery data) and an existing /boot
partition from a previous install
In partman, I did the following:
a) highlighted the /dev/sda3 (was /boot), partman tells me it is not
using the partition, I changed it to be /boot and ext2
b) I ran the partman LVM menu and deleted the existing two LVs and then
I deleted the VG
c) I returned to the main partman menu and deleted the two partitions
that were used by LVM:
sda5 (40GB)
sda6 (250GB)
d) I then created a new partition:
sda5 (400GB) type 8e
e) then I ran the partman LVM menu again. On entering the menu, it
reports that sda5 = 40GB (the old size). No mention of sda6
f) then I go to a shell and run fdisk /dev/sda
It shows me the correct partition sizes for sda4 (extended) and sda5
(type 8e for LVM)
g) if I back out of the LVM config menu and go back in again, same problem
h) I accept the dodgy values and let it create the volume group. Then I
run pvscan. It shows me /dev/sda5 = 37.25 GB (the wrong value)
i) if I manually create the VG, it is fine:
pvcreate -ff /dev/sda5
vgcreate vg00 /dev/sda5
pvscan (now shows correct output)
Therefore, I believe the wrong value was cached somewhere within partman
Reply to: