[Bug 1357093] Re: LVM or Encrypted install creates too small /boot partition

[TJ]

The issue here isn't so much the absolute space initially allocated to
the /boot/ LV, it is that the installer allocates 100% of the Volume
Groups space.

The great advantage of LVM is that space can by dynamically allocated
and removed from Logical Volumes as needed.

If the installer were to leave 5% of the Volume Group unallocated it
would be possible for the system to detect this out-of-space condition
and extend the /boot/ LV:

lvextend -l 50%FREE VG/boot
resize2fs /dev/mapper/VG-boot # assuming ext file-system

and at the same time display a prominent warning and options for
automatically removing the superseded kernel versions.

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

Title:
  LVM or Encrypted install creates too small /boot partition

Status in “ubiquity” package in Ubuntu:
  Confirmed

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

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