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

Groups > linux.debian.kernel > #83071 > unrolled thread

Bug#1076539: plymouth: Updating plymouth fails with "No space left on device"

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Laurent Bigonville <bigon@debian.org> - 2024-07-18 11:20 +0200
    Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Diederik de Haas <didi.debian@cknow.org> - 2024-07-18 11:50 +0200

#83071 — Bug#1076539: plymouth: Updating plymouth fails with "No space left on device"

Le 18/07/24 à 10:54, Diederik de Haas a écrit :
> Control: severity -1 minor
>
> [...]
> I fail to see how this is any package's problem.
> Your boot partition is too small to perform the requested operation.
>
> During compression it needs the space for the uncompressed files and
> the space needed for the compressed archive, so it generally needs
> (much) more space then it finally needs as the uncompressed files will
> be removed again once the compressed archive is complete.
>
> Solution: make your boot partition larger. Or remove older/other
> kernels, but IMO this will only delay the inevitable.
>
> Reducing severity to minor, but I actually think it should just be closed.
>
> On 18 Jul 2024 10:17:20 +0200 Laurent Bigonville <bigon@debian.org> wrote:
>> It's related to firmware-misc-nonfree that is now pulling
>> firmware-nvidia-graphics that contains a lot of (non-free) firmwares.
>>
>> With firmware-nvidia-graphics installed, my initramfs grows to something
>> like 200M compared to 64M without it.
> The firmware-nvidia-graphics package was created exactly because its size
> got big(ger) and (partially therefor) deserved its own package instead of
> making the firmware-misc-nonfree extremely large. That package is meant
> for 'the other' firmware which don't deserve their own package.
> The firmware-nvidia-graphics is recommended by firmware-misc-nonfree as
> the nvidia graphics firmware files were moved from the latter to the former.
>
> Solution: If you don't need firmware-nvidia-graphics, don't install it.
> If you do need it, but don't have the space for it, then increase your
> storage size.

Well you change expectation from users that have firmware-misc-nonfree 
installed by pulling that huge package

IMVHO, a lot of people with firmware-misc-nonfree installed will 
experience an issue when updating.

The /boot partition size I've here is the default one from the 
debian-installer

[toc] | [next] | [standalone]

#83073

[Multipart message — attachments visible in raw view] — view raw

On Thursday, 18 July 2024 11:11:23 CEST Laurent Bigonville wrote:
> Well you change expectation from users that have firmware-misc-nonfree
> installed by pulling that huge package

I fail to see how. If those files weren't split into their own packages, the 
updated/new firmware-misc-nonfree would've contained the firmware of
the 'old' misc-nonfree + nvidia-graphics + intel-graphics + mediatek/ralink + 
new files that would otherwise have been added for misc-nonfree.

See also https://bugs.debian.org/1057786

> IMVHO, a lot of people with firmware-misc-nonfree installed will
> experience an issue when updating.

You should've seen a NEWS entry informing you of the changes.
If that didn't happen, that's a problem/bug.

On donderdag 18 juli 2024 11:14:35 CEST you wrote:
> On 18.07.24 11:11, Laurent Bigonville wrote:
> > The /boot partition size I've here is the default one from the
> > debian-installer
> 
> This seems to be the core of the problem. In my case it is 500MB, and
> was the default from the install. So many users will be affected by default.

I do agree with that. And the kernel size growing bigger contributed to that 
becoming a (bigger) problem. (There are bug reports about that)

When I set up my system, I made /boot 2G because I foresaw this problem
(and I intended to do a bit more with kernels then the average user).

I think a very valid argument can be made to change the default in d-i,
but to be blunt: you *accepted* the *defaults*.

But most people are probably not as experienced with Debian as the two of you 
which in turn would make me point out the same problem, but be more subtle/
gentle about it.

Still, "No space left on device" is not a packaging problem.

Cheers,
  Diederik

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web