package update proceeds without adequate disk space

Bug #126774 reported by Christopher Barrington-Leigh
34
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
Triaged
Medium
Dereck Wonnacott

Bug Description

Binary package hint: apt

I ran "apt-get dist-upgrade" for a big upgrade. The apt checked to see whether I had enough disk space to download all the files (ie I didn't at first, and it refused to upgrade. I made more space). But that is inadequate space, as there needs to be enough both to download the files and to install them! So the installer crashed in a horrible way when the disk ran out of space, and messed up my distribution.

The installer should refuse to install new packages if there is not adequate space on the disk for them!

Revision history for this message
Christopher Barrington-Leigh (cpbl) wrote :

I was using Feisty's latest version of apt, by the way.

Michael Vogt (mvo)
Changed in apt:
status: New → Confirmed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

This seems to be pretty common, a lot of false positives because a system partition is filled during package upgrade, usually due to the kernel.

Changed in apt:
importance: Undecided → Medium
Revision history for this message
Kosta (kosta-fillibach) wrote :

im using hardy. theres a lot of kernel upates and /boot is pretty small. I have to delete old kernels all the time because the update tries to install a new one without taking care of disk space...

Changed in apt:
status: Confirmed → Triaged
Revision history for this message
Dereck Wonnacott (dereck) wrote :
Changed in apt:
assignee: nobody → dereck
status: Triaged → In Progress
Revision history for this message
Dereck Wonnacott (dereck) wrote :

This will not solve Kosta's problem, but apt-get will now take into consideration that it must download the packages before it can install them when calculating the space requirements.

Changed in apt:
status: In Progress → Triaged
Revision history for this message
Dereck Wonnacott (dereck) wrote :

This is a difficult problem.

The package information only tells us how big the installed fileset is. We also know the package size before installation. We do not truely know where a package will put files until the installer runs.

If the user uses a custom partitioning scheme such as yourself, we need to open ever package, extract where files are to be placed, sum the file size for ever one of the 100's of packages to upgrade. Then make the desicion on whether it will fit or not.

In addition to that challenge, some packages download more data after installation, think flash and mscorefonts. The only way to be sure those package would fit is to install them and see if the data will fit.

I think this is reason enough for 'wont fix' seeing that anything that we do will make the already painfully long install process longer. It works with the default and recommended disk configuration of a single / partition. If a user changes the disk configuration he should now know the consequences.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.