group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #10597
[Bug 1646222] Re: calculation of needed free space in /boot is inaccurate and causes refusal to upgrade
This bug was fixed in the package ubuntu-release-upgrader - 1:16.04.21
---------------
ubuntu-release-upgrader (1:16.04.21) xenial; urgency=medium
* DistUpgrade/DistUpgradeCache.py: import kernel initrd size estimation
code from update-manager (since u-r-u is the only consumer of it) and
refactor in order to give more accurate estimates. LP: #1646222.
-- Steve Langasek <steve.langasek@xxxxxxxxxx> Thu, 22 Dec 2016
00:05:53 -0600
** Changed in: ubuntu-release-upgrader (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1646222
Title:
calculation of needed free space in /boot is inaccurate and causes
refusal to upgrade
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in update-manager package in Ubuntu:
Triaged
Status in ubuntu-release-upgrader source package in Xenial:
Fix Released
Status in update-manager source package in Xenial:
Won't Fix
Status in ubuntu-release-upgrader source package in Yakkety:
In Progress
Status in update-manager source package in Yakkety:
Won't Fix
Bug description:
[SRU Justification]
In some configurations, update-manager will refuse to upgrade kernel packages, citing lack of space in /boot even though there is enough space in /boot and if the upgrade is done with 'apt dist-upgrade', it succeeds. Affected users may as a result fail to have security updates applied to their system, unless they know how to run apt from the commandline or have unattended upgrades enabled.
[Test case]
1. Check the space currently used on /boot with du -sh.
2. Create a partition 120MB larger than the space used on /boot.
3. Copy the contents of your /boot directory into this partition.
4. Mount this partition as /boot.
5. Configure your system so that a newer kernel ABI is available (e.g., by enabling -proposed; or by waiting for the next kernel update to publish; or by downgrading the kernel using apt-get and rebooting).
6. Run update-manager.
7. Verify that update-manager refuses to upgrade, citing a lack of space in /boot.
8. Install python3-distupgrade and ubuntu-release-upgrader-core from -proposed.
9. Re-run update-manager.
10. Verify that update-manager proceeds with the upgrade, and that the upgrade succeeds, with no failure due to lack of disk space on /boot.
11. Repeat steps 2-9 with a partition that is only 60MB larger than the space used on /boot.
12. Verify that update-manager still refuses to proceed with the upgrade, with the packages from -proposed.
[Regression potential]
Since this changes the limit at which update-manager refuses to upgrade due to lack of free space, if the new calculation of the minimum required free space is too low, users may see update-manager proceed with the upgrade, then fail at the dpkg stage, requiring manual recovery.
[Original report]
I have a /boot partition which is sized just right to accommodate 3 kernels, plus a little bit of overhead.
$ df -h /boot/
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 280M 144M 118M 56% /boot
$
Previously, update-manager had no problem letting me upgrade kernels.
With the latest kernel update in 16.10, I got an error message that I
needed more free space on this filesystem.
After bypassing update-manager with 'sudo apt dist-upgrade', the
filesystem's usage looks like this:
$ df -h /boot/
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 280M 206M 56M 79% /boot
$
So update-manager is getting the disk usage requirement for /boot off
by a factor of 2 (at least? I didn't save the error message from the
dialog).
It's better to refuse to upgrade than to fail mid-upgrade due to disk
space, but not if that means getting stuck forever with an old kernel
unnecessarily.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: update-manager 1:16.10.7
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Nov 30 12:10:25 2016
GsettingsChanges:
b'com.ubuntu.update-manager' b'show-details' b'true'
b'com.ubuntu.update-manager' b'window-height' b'551'
b'com.ubuntu.update-manager' b'first-run' b'false'
b'com.ubuntu.update-manager' b'window-width' b'813'
b'com.ubuntu.update-manager' b'launch-time' b'1480522730'
InstallationDate: Installed on 2010-09-24 (2259 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
PackageArchitecture: all
SourcePackage: update-manager
UpgradeStatus: Upgraded to yakkety on 2016-10-28 (32 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1646222/+subscriptions