Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #67047

Bug#960181: pigz: abort: write error on <stdout> (No space left on device)

Cross-posted to 2 groups.

Show all headers | View raw

On 2020-05-10 4:59 a.m., Rainer Dorsch wrote:
> It is weird that mkinitramfs reports no space left on device, but df does not confirm this. So it might be "another" device (like initramfs?). I am aware that I include a virtualbox module with dkms
df does, in a fashion confirm it.  It shows 91% in use for /boot. The 
issue is that you are probably attempting to another kernel version into 
/boot.  Try removing previous versions to free up space.

I had a similar problem where my initramfs became big due to too many 
firmware files being included, and therefore couldn't fit multiple 
initramfs variants in /boot.

Some background:
https://blog.raymond.burkholder.net/index.php?/archives/1008-pigz-abort-write-error-on-stdout-No-space-left-on-device.html



>
> Calculating upgrade... Done
> The following package was automatically installed and is no longer required:
>    linux-image-4.19.0-6-amd64
> Use 'apt autoremove' to remove it.
> Setting up initramfs-tools (0.133+deb10u1) ...
> update-initramfs: deferring update (trigger activated)
> Processing triggers for initramfs-tools (0.133+deb10u1) ...
> update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64
> pigz: abort: write error on <stdout> (No space left on device)
> E: mkinitramfs failure cpio 141 pigz 28
> update-initramfs: failed for /boot/initrd.img-4.19.0-9-amd64 with 1.
> dpkg: error processing package initramfs-tools (--configure):
>   installed initramfs-tools package post-installation script subprocess returned error exit status 1
> Errors were encountered while processing:
>   initramfs-tools
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> root@h370:~# df
> Filesystem                1K-blocks      Used Available Use% Mounted on
> udev                       16364780         0  16364780   0% /dev
> tmpfs                       3278936      9768   3269168   1% /run
> /dev/mapper/b370--vg-root 486574264 416572764  45215172  91% /
> tmpfs                      16394664     78848  16315816   1% /dev/shm
> tmpfs                          5120         4      5116   1% /run/lock
> tmpfs                      16394664         0  16394664   0% /sys/fs/cgroup
> /dev/sda2                    241965    206789     22684  91% /boot
> /dev/sda1                    523248       140    523108   1% /boot/efi
> tmpfs                       3278932        28   3278904   1% /run/user/2809
> root@h370:~#
>

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#960181: pigz: abort: write error on <stdout> (No space left on device) Rainer Dorsch <ml@bokomoko.de> - 2020-05-10 13:10 +0200
  Bug#960181: pigz: abort: write error on <stdout> (No space left on device) Raymond Burkholder <ray@oneunified.net> - 2020-05-10 15:30 +0200
    Bug#960181: pigz: abort: write error on <stdout> (No space left on device) Rainer Dorsch <ml@bokomoko.de> - 2020-05-10 16:10 +0200
      Bug#960181: pigz: abort: write error on <stdout> (No space left on device) Ben Hutchings <ben@decadent.org.uk> - 2020-05-10 18:20 +0200
  Bug#960181: marked as done (pigz: abort: write error on <stdout>  (No space left on device)) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-05-10 15:50 +0200

csiph-web