[Bug 1367601] Re: kickstart physical volume consumes entire disk

[Morty]

BTW: I also tried setting --maxsize and removing the --fstype.  No joy.
Like so:

clearpart --all --initlabel
part /boot   --size 256                   --asprimary  --fstype ext3
part pv.01   --size 12000 --maxsize 12500 --asprimary  
part pv.02   --size 3000 --maxsize 3200   --asprimary  

volgroup sysvg1 pv.01
volgroup usrvg1 pv.02

logvol /     --vgname=sysvg1  --size=8000     --name=root
logvol /var  --vgname=sysvg1  --size=2000      --name=var  --grow
logvol swap  --vgname=sysvg1  --size=1000     --name=swap --fstype=swap

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

Title:
  kickstart physical volume consumes entire disk

Status in “kickseed” package in Ubuntu:
  New

Bug description:
  I'm trying to build a kickstart config that looks like so:

  clearpart --all --initlabel
  part /boot   --size 256    --asprimary  --fstype ext3
  part pv.01   --size 50000  --asprimary  --fstype ext3
  part pv.02   --size 10000      --asprimary  --fstype ext3 --grow

  volgroup sysvg1 pv.01
  volgroup usrvg1 pv.02

  logvol /     --vgname=sysvg1  --size=20480     --name=root
  logvol /var  --vgname=sysvg1  --size=20480     --name=var  --grow
  logvol swap  --vgname=sysvg1  --size=8192      --name=swap --fstype=swap

  Under  12.04, this kind of thing worked great.  Under 14.04, pv.01
  consumes the entire disk, and then pv.02 never gets created.  This is
  true even though the disk is much larger than the size specified for
  pv.01.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kickseed/+bug/1367601/+subscriptions