Bug#517935: debian-installer: partman-auto/expert_recipe minimum size sanity check counts both LVM VG and LV
Package: debian-installer
Severity: normal
Version: 20090123
While preparing the presseding file for our fully automated Lenny
workstation installation I ran into the following bug:
The following recipe works fine on a 80026 MB:
d-i partman-auto/expert_recipe string \
dphys-ws-part :: \
256 10000000 512 ext3 \
$primary{ } $bootable{ } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } \
mountpoint{ /boot } \
. \
61440 1000000 100000000 lvm \
$primary{ } $defaultignore{ } \
method{ lvm } vg_name{ vg0 } \
. \
15248 40000 46080 ext3 \
$lvmok{ } in_vg{ vg0 } lv_name{ root } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } \
mountpoint{ / } \
. \
2048 10000 10240 ext3 \
$lvmok{ } in_vg{ vg0 } lv_name{ data } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } \
mountpoint{ /export/data1 } \
. \
1024 2000 10240 ext3 \
$lvmok{ } in_vg{ vg0 } lv_name{ scr } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } \
mountpoint{ /scratch } \
. \
10 1000 1048576 ext3 \
$lvmok{ } in_vg{ vg0 } lv_name{ dummy } \
method{ keep } \
.
And the following does not and the default recipe (root + swap) is
used instead:
d-i partman-auto/expert_recipe string \
dphys-ws-part :: \
256 10000000 512 ext3 \
$primary{ } $bootable{ } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } \
mountpoint{ /boot } \
. \
61440 1000000 100000000 lvm \
$primary{ } $defaultignore{ } \
method{ lvm } vg_name{ vg0 } \
. \
15249 40000 46080 ext3 \
$lvmok{ } in_vg{ vg0 } lv_name{ root } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } \
mountpoint{ / } \
. \
2048 10000 10240 ext3 \
$lvmok{ } in_vg{ vg0 } lv_name{ data } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } \
mountpoint{ /export/data1 } \
. \
1024 2000 10240 ext3 \
$lvmok{ } in_vg{ vg0 } lv_name{ scr } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } \
mountpoint{ /scratch } \
. \
10 1000 1048576 ext3 \
$lvmok{ } in_vg{ vg0 } lv_name{ dummy } \
method{ keep } \
.
The only difference: The minimal / LV size grew from 15248 to 15249.
You can easily check that minimum boot partition size plus minimal VG
size fit onto the disk without problems and that all the remaining
partitions fit into the VG with their minimal size.
But the installer seems to sum up all minimal sizes independent of
being LVM volume groups or LVM logical volumes. The first recipe has a
sum of all minimal sizes of 80026 and the second one has 80027. So the
second recipe is ignored on that disk.
So this basically prohibits to create a / LV with a minimal size of 45
GB on a 80 GB disk.
I though can workaround by setting the priority of the / LV so high
that it gets nearly the maximum wanted size (as shown in the examples
above).
Happened with i386 installer btw, haven't checked the amd64 yet, but I
don't expect this to be architecture dependent.
-- System Information:
Debian Release: 4.0
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.26.3-amd64-1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Reply to: