Please advise as to what computer janitor program we should download that would be effective against this bug.
Sent from my MetroPCS 4G Wireless Phone
<div>-------- Original message --------</div><div>From: Peter Ruibal <email address hidden> </div><div>Date:05/23/2015 1:02 AM (GMT-08:00) </div><div>To: <email address hidden> </div><div>Cc: </div><div>Subject: [Bug 798414] Re: update-initramfs should produce a more helpful error
when there isn't enough free space </div><div>
</div>I just go this for the fourth time in two years and finally decided to
follow up.
Some questions:
Won't every Ubuntu user *eventually* hit this? Can we expect them to
google around, run random junk in a terminal, and hope things go
smoothly after that?
Should the install scripts just be able to uninstall old kernels on its
own if it detects there's not enough space? What happens if their
current kernel has a critical security vulnerability? Would they just
stay vulnerable forever?
When generating a new initramfs there is no check for available free
space, subsequently its possible for update-initramfs to fail due to a
lack of free space. This is resulting in package installation
failures for initramfs-tools. For example:
Setting up initramfs-tools (0.98.8ubuntu3) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic
gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
dpkg: error processing initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
WORKAROUND:
Remove unused kernels using computer janitor or manually free space on
your partition containing the /boot file system.
Please advise as to what computer janitor program we should download that would be effective against this bug.
Sent from my MetroPCS 4G Wireless Phone
<div>-------- Original message ------- -</div> <div>From: Peter Ruibal <email address hidden> </div>< div>Date: 05/23/2015 1:02 AM (GMT-08:00) </div><div>To: <email address hidden> </div><div>Cc: </div><div>Subject: [Bug 798414] Re: update-initramfs should produce a more helpful error
when there isn't enough free space </div><div>
</div>I just go this for the fourth time in two years and finally decided to
follow up.
Some questions:
Won't every Ubuntu user *eventually* hit this? Can we expect them to
google around, run random junk in a terminal, and hope things go
smoothly after that?
Should the install scripts just be able to uninstall old kernels on its
own if it detects there's not enough space? What happens if their
current kernel has a critical security vulnerability? Would they just
stay vulnerable forever?
-- /bugs.launchpad .net/bugs/ 798414
You received this bug notification because you are subscribed to the bug
report.
https:/
Title:
update-initramfs should produce a more helpful error when there isn't
enough free space
Status in tools for generating an initramfs:
Confirmed
Status in NULL Project:
Fix Released
Status in initramfs-tools package in Ubuntu:
Triaged
Bug description:
Binary package hint: initramfs-tools
When generating a new initramfs there is no check for available free
space, subsequently its possible for update-initramfs to fail due to a
lack of free space. This is resulting in package installation
failures for initramfs-tools. For example:
Setting up initramfs-tools (0.98.8ubuntu3) ... img-2.6. 38-8-generic
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.
gzip: stdout: No space left on device img-2.6. 38-8-generic
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.
dpkg: error processing initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
WORKAROUND:
Remove unused kernels using computer janitor or manually free space on
your partition containing the /boot file system.
To manage notifications about this bug go to: /bugs.launchpad .net/initramfs- tools/+ bug/798414/ +subscriptions
https:/