[Bug 1133052] Re: installer unable to create multiple lvm volume groups

Fabio Marconi fabiomarconi at ubuntu.com
Wed Feb 27 12:46:58 UTC 2013


** Package changed: ubuntu => partman-base (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to partman-base in Ubuntu.
https://bugs.launchpad.net/bugs/1133052

Title:
  installer unable to create multiple lvm volume groups

Status in “partman-base” package in Ubuntu:
  New

Bug description:
  I'm not sure with which package this bug should be associated as it
  likely will span multiple (debian-installer,partman-lvm at the least)

  I'm unable to create multiple volume groups via the kickstart
  installation method.

  The following partitioning information in the kickstart file:
  part /boot   --size 1024    --asprimary  --fstype ext3 --ondisk=1

  part pv.01   --size 40960  --asprimary  --fstype ext3 --ondisk=1
  volgroup sysvg1 pv.01

  part pv.02   --size 1      --asprimary  --fstype ext3 --ondisk=1 --grow
  volgroup usrvg1 pv.02

  results in a single volume group called sysvg1 and another named after
  the machine's hostname. It attempts to create usrvg1 using the same
  device as that used for sysvg1.

  I believe the immediate cause of this is in /lib/partman/lib/auto-
  lvm.sh in  auto_lvm_create_vg_map(). The recipe_device variable should
  contain the physical device to use for the given partition, however
  there I don't believe any device{} tag is ever set. Looking at the
  output of /tmp/expert_recipe seems to support this:

  256 256 256 ext3 $primary{ } method{ format } format{ } use_filesystem{ } filesystem{ ext3 } mountpoint{ /boot } . \
   40960 40960 40960 ext3 $primary{ } $defaultignore{ } method{ lvm } vg_name{ sysvg1 } . \
   1 1073741824 -1 ext3 $primary{ } $defaultignore{ } method{ lvm } vg_name{ usrvg1 } . 

  The bigger issue I think is that the physical volume/volume group
  relationships are stripped after kickseed initially parses the
  partitioning section in the kickstart file. Perhaps the mountpoint{}
  tag could be used to contain the PV <-> vg mappings.

  Thanks!

  -Aaron

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/1133052/+subscriptions




More information about the foundations-bugs mailing list