[Bug 433092] Re: preseed LVM partition recipe broken
ritesh
433092 at bugs.launchpad.net
Thu Aug 11 08:23:24 UTC 2022
Finally, able to fix number of partition issues, however size of
partition needs to be checked. Below is updated code, hope this helps. I
will update if partition size is fixed as well.
d-i partman-auto/disk string /dev/sda
d-i partman-auto/method string lvm
d-i partman-lvm/device_remove_lvm boolean true
d-i partman-md/device_remove_md boolean true
d-i partman-auto-lvm/new_vg_name string main
d-i partman-auto-lvm/guided_size string max
d-i partman-auto/choose_recipe select multi
d-i partman-auto-lvm/new_vg_name string vgroot
d-i partman-auto/expert_recipe string \
boot-root :: \
1024 10 1024 ext4 \
$primary{ } $bootable{ } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext4 } \
mountpoint{ /boot } \
. \
100 11 -1 ext4 $primary{ } \
$defaultignore{ } \
method{ lvm } \
device{ /dev/sda } \
vg_name{ vgroot } \
. \
4096 20 5120 ext4 \
$lvmok{ } \
in_vg{ vgroot } \
lv_name{ lvopt } \
method{ lvm } format{ } \
use_filesystem{ } filesystem{ ext4 } \
mountpoint{ /opt } \
. \
1900 60 2000 ext4 \
$lvmok{ } \
in_vg{ vgroot } \
lv_name{ lvhome } \
method{ lvm } format{ } \
use_filesystem{ } filesystem{ ext4 } \
mountpoint{ /home } \
. \
7168 30 8192 ext4 \
$lvmok{ } \
in_vg{ vgroot } \
lv_name{ lvvar } \
method{ lvm } format{ } \
use_filesystem{ } filesystem{ ext4 } \
mountpoint{ /var } \
. \
4096 40 5120 ext4 \
$lvmok{ } \
in_vg{ vgroot } \
lv_name{ lvtmp } \
method{ lvm } format{ } \
use_filesystem{ } filesystem{ ext4 } \
mountpoint{ /tmp } \
. \
4096 50 5120 ext4 \
$lvmok{ } \
in_vg{ vgroot } \
lv_name{ lvvartmp } \
method{ lvm } format{ } \
use_filesystem{ } filesystem{ ext4 } \
mountpoint{ /var/tmp } \
. \
2000 12 2000 linux-swap \
$lvmok{ } \
in_vg{ vgroot } \
lv_name{ lvswap } \
method{ swap } format{ } \
. \
9216 15 10240 ext4 \
$lvmok{ } \
in_vg{ vgroot } \
lv_name{ lvroot } \
method{ lvm } format{ } \
use_filesystem{ } filesystem{ ext4 } \
mountpoint{ / } \
. \
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman-lvm/confirm boolean true
d-i partman-lvm/confirm_nooverwrite boolean true
d-i partman-lvm/device_remove_lvm boolean true
d-i partman/choose_partition select finish
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to partman-auto-lvm in Ubuntu.
https://bugs.launchpad.net/bugs/433092
Title:
preseed LVM partition recipe broken
Status in partman-auto-lvm package in Ubuntu:
Triaged
Bug description:
Binary package hint: partman-base
I've spent weeks working with preseed LVM partitioning. I've come to the conclusion that there is little relationship between the sizes in a recipe and the actual allocations. The first couple of partitions in a recipe are OK, but then they wildly diverge.
I've made some test cases, that include the preseed files, the partman logs and the resultant lvs output.
In the first case, partman.ok1, the last partition is dropped
completely. I removed it from the 2nd and 4rd test cases to simplify
the test case.
I expected partman would vary the partition size.
The following attachment is a tgz containing:
partman.ok1
partman.ok2
partman.ok3
These are all variants of the LVM partition in the partman recipe preseed files, the parman logs, and lvs output.
The requested sizes vary by a factor of 10 but the resultant partitions barely change at all.
This is from jaunty, but I verified the same behavior with karmic
alpha 5 as well.
The partman packages are the default ones provided on the alternate
install CD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto-lvm/+bug/433092/+subscriptions
More information about the foundations-bugs
mailing list