I have a kickstart file with the following partitioning directives:
part /boot --fstype ext3 --onpart=sda1 part pv.100000 --onpart=sda2 --noformat volgroup vol0 pv.100000 --noformat logvol / --vgname=vol0 --name=lvol1 --useexisting --fstype=ext4 logvol /tmp --vgname=vol0 --name=lvol2 --useexisting --fstype=ext4 logvol swap --vgname=vol0 --name=lvol3 --useexisting logvol /data --vgname=vol0 --name=lvol4 --noformat
The purpose is reinstalling a machine with a given partitioning scheme and preserve files on /data across the reinstall.
Kickstarting a machine with these instructions, it comes up without the /data partition, it is not mounted and not in fstab. But the lvol exists and can be mounted manually, with all data preserved.
/root/anaconda-ks.cfg shows the following:
#part /boot --fstype=ext3 --onpart=sda1 #part pv.008002 --onpart=sda2 --noformat
#volgroup vol0 --pesize=32768 --useexisting --noformat pv.008002 #logvol / --fstype=ext4 --name=lvol1 --vgname=vol0 --useexisting #logvol /tmp --fstype=ext4 --name=lvol2 --vgname=vol0 --useexisting #logvol swap --name=lvol3 --vgname=vol0 --useexisting #logvol --name=lvol4 --vgname=vol0 --useexisting --noformat
I.e. the mount point was dropped.
Any ideas why this might be happening? I couldn't find anything related in the migration guide, and this looks like a bug to me.
Any ideas why this might be happening? I couldn't find anything related in the migration guide, and this looks like a bug to me.
During installation:
# lvdisplay ... --- Logical volume --- LV Name /dev/vol0/lvol4 VG Name vol0 LV UUID 90lEKP-f8EW-qxpc-i1WI-vnRn-npfu-fQ6C8A LV Write Access read/write LV Status NOT available <<<<< LV Size 422.25 GiB Current LE 13512 Segments 1 Allocation inherit Read ahead sectors auto # lvscan ACTIVE '/dev/vol0/lvol1' [25.00 GiB] inherit ACTIVE '/dev/vol0/lvol2' [10.00 GiB] inherit ACTIVE '/dev/vol0/lvol3' [8.00 GiB] inherit inactive '/dev/vol0/lvol4' [422.25 GiB] inherit #