[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#992345: www.debian.org: bullseye release-notes are misleading about the needed disk space



Hi Cyril,

On 2021-08-17 18:01:44 +0200, Cyril Brulebois wrote:
> Hi Vincent,
> 
> Vincent Lefevre <vincent@vinc17.net> (2021-08-17):
> > 649 upgraded, 113 newly installed, 11 to remove and 1 not upgraded.
> > Need to get 455 MB of archives.
> > After this operation, 558 MB of additional disk space will be used.
> > 
> > and I had around 650 MB free space
> 
> 455+558 >> 650 so it was very unlikely to work?

This is what I was wondering initially, but the release notes say:

  If you do not have enough space for the upgrade, apt will warn you
  with a message like this:
  E: You don't have enough free space in /var/cache/apt/archives/.

i.e. if the test was 455+558 < 650, the lack of space would be
detectable by apt, so that I should have got a warning. Since I
didn't get the warning, I supposed that the 455 MB were included in
the 558 MB (the last message is not clear: "additional disk space"
compared to the status before or after the download?).

> > I suspect that some packages like this one need a lot of temporary
> > disk space (could this be related to initrd before compression?).
> > But there is nothing about that in the release notes. And perhaps
> > a warning should have been output by apt.
> 
> There's one for the directory where debs are downloaded (which you
> didn't get since 455 << 650), but I suspect it's harder to estimate
> where the whole “additional disk space” is going to end up,
> depending on file system layout, etc.?

The text from the release notes clearly says "for the upgrade", not
"for the download of the archives". Thus the comparison would have
been 455+558 vs 650 if 455 is not included in the 558. Perhaps it
should assume that everything goes to the same partition since
AFAIK, this is the most common case (optionally check whether
/var/cache/apt/archives and / are on different partitions); this
is just a warning after all.

In my case, there's a second disk, but mounted on /srv. So this
shouldn't count.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


Reply to: