[Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Brian Murray]

I've verified that the version of dkms, 2.3-3ubuntu1.2, in zesty-
proposed now does the right thing.

Backing up initrd.img-4.10.0-19-generic to /boot/initrd.img-4.10.0-19-generic.old-dkms
Making new initrd.img-4.10.0-19-generic
(If next boot fails, revert to initrd.img-4.10.0-19-generic.old-dkms image)
update-initramfs...

DKMS: uninstall completed.
removed '/boot/initrd.img-4.10.0-19-generic.old-dkms'
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.10.0-19-generic /boot/vmlinuz-4.10.0-19-generic
update-initramfs: Deleting /boot/initrd.img-4.10.0-19-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.10.0-19-generic /boot/vmlinuz-4.10.0-19-generic
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.10.0-37-generic
Found initrd image: /boot/initrd.img-4.10.0-37-generic
Found linux image: /boot/vmlinuz-4.10.0-28-generic
Found initrd image: /boot/initrd.img-4.10.0-28-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done
bdmurray at clean-zesty-amd64:~$ ls -lh /boot/
total 149M
-rw-r--r-- 1 root root 1.4M Jun 29 02:14 abi-4.10.0-28-generic
-rw-r--r-- 1 root root 1.4M Oct  6 12:45 abi-4.10.0-37-generic
-rw-r--r-- 1 root root 201K Jun 29 02:14 config-4.10.0-28-generic
-rw-r--r-- 1 root root 201K Oct  6 12:45 config-4.10.0-37-generic
drwxr-xr-x 5 root root 4.0K Oct 10 09:33 grub
-rw-r--r-- 1 root root  42M Oct 10 09:26 initrd.img-4.10.0-28-generic
-rw-r--r-- 1 root root  41M Oct 10 09:26 initrd.img-4.10.0-28-generic.old-dkms
-rw-r--r-- 1 root root  42M Oct 10 09:29 initrd.img-4.10.0-37-generic
-rw-r--r-- 1 root root 179K Jan 28  2016 memtest86+.bin
-rw-r--r-- 1 root root 181K Jan 28  2016 memtest86+.elf
-rw-r--r-- 1 root root 181K Jan 28  2016 memtest86+_multiboot.bin
-rw------- 1 root root 3.6M Jun 29 02:14 System.map-4.10.0-28-generic
-rw------- 1 root root 3.6M Oct  6 12:45 System.map-4.10.0-37-generic
-rw------- 1 root root 7.3M Jun 29 02:14 vmlinuz-4.10.0-28-generic
-rw------- 1 root root 7.3M Oct  6 12:45 vmlinuz-4.10.0-37-generic


** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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