[dist-upgrade] "not enough disk space" should mention amount needed

[wvengen]

Binary package hint: update-manager

When doing a dist-upgrade from the update-manager, a dialog is presented in the 3rd step "Downloading and installing the upgrades" titled "Not enough free disk space" with the text: "The upgrade aborts now. Please free at least 128M of disk space on /var/cache/apt/archives/. Empty your trash and remove temporary packages of former installations using 'sudo apt-get clean'."

The message was correct, but I expected to (also) see the amount of disk space needed in total for doing the upgrade, so I could remove things until there was enough. Currently I have to remember how much free disk space there was at the start of my cleanup action.

Suggestion: don't only mention how much _more_ disk space is required also mention the total disk space needed for upgrading.

[TiagoCruz (tiagocruz)]

So... update-manager give one warning around disk space?

Good... because yesterday I did one remote upgrade (edgy/ festy) using apt/dpkg and I think that it don't calcule the necessary disk space, after download... when starts to install the packages.

My disk space was over when the new kernel was installing... so... the machine don't got the successful reboot :)

I need to launch the 'clean' on apt cache, and start the upgrade again... but inside of one chroot, using one live-cd to complete the upgrade.

Thanks

[Matthias Meulien (orontee)]

I had the same problem as TiagoCruz... It seems that the computation of needed space is wrong. Here are the last ten lines of my log file /var/log/dist-upgrade/term.log:

Paramétrage de initramfs-tools (0.85eubuntu10) ...
Installation de la nouvelle version du fichier de configuration /etc/initramfs-tools/initramfs.conf ...
update-initramfs: Generating /boot/initrd.img-2.6.17-11-generic
cp: ne peut évaluer `/etc/udev/rules.d/85-brltty.rules': Aucun fichier ou répertoire de ce type
cp: ne peut évaluer `/etc/udev/rules.d/05-options.rules': Aucun fichier ou répertoire de ce type
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
W: mdadm: falling back to emergency procedure in initramfs.
Paramétrage de volumeid (108-0ubuntu4) ...
gzip: stdout: No space left on device

[Michael Vogt (mvo)]

@Matthias Meulien:
Thanks for your bugreport.

Can you please attach the files in /var/log/dist-upgrade ? This will help us diagnose the problem and figure if there is a bug in the free space checking code. Please also include the output of:
$ df -h

Thanks,
 Michael

[wvengen (wvengen)]

I'd suggest to open a new bug report for free-space computation issues, this bug is merely a wishlist-item for adding the amount of diskspace needed to the message.

[Matthias Meulien (orontee)]

I attached the content of /var/log/dist-upgrade. I think the following output is not relevant because I've removed hundreds of package to re-run the update-manager.

~$ df
Sys. de fich. Tail. Occ. Disp. %Occ. Monté sur
/dev/hda1 7,2G 3,3G 3,7G 47% /
varrun 379M 100K 379M 1% /var/run
varlock 379M 4,0K 379M 1% /var/lock
procbususb 379M 128K 379M 1% /proc/bus/usb
udev 379M 128K 379M 1% /dev
devshm 379M 0 379M 0% /dev/shm
lrm 379M 33M 346M 9% /lib/modules/2.6.20-15-generic/volatile
/dev/mapper/hda5 30G 6,6G 22G 24% /home
/dev/mapper/hdb1 4,6G 1,8G 2,7G 40% /var/local/archives
/dev/mapper/hdb2 15G 13G 1,3G 91% /var/local/music

[Steve Strobel (steve-strobel)]

I would suggest changing the wording of the message to, "The upgrade aborts now. Please free at least 128M _MORE_ disk space". I originally read the message as, "Make sure you have at least 128M free", when it actually means, "You are short by 128M". Mentioning the total amount of space needed would also help minimize confusion.

[Paul Flint (flint)]

Dear Michael,

THANKS!!!

Regards,

Flint

On Sat, 8 Sep 2007, Michael Vogt wrote:

> Date: Sat, 08 Sep 2007 09:08:36 -0000
> From: Michael Vogt <email address hidden>
> Reply-To: Bug 46775 <email address hidden>
> To: <email address hidden>
> Subject: [Bug 46775] Re: [dist-upgrade] "not enough disk space" should mention
> amount needed
>
> ** Changed in: update-manager (Ubuntu)
> Status: Fix Committed => Fix Released
>
> --
> [dist-upgrade] "not enough disk space" should mention amount needed
> https://bugs.launchpad.net/bugs/46775
> You received this bug notification because you are a direct subscriber
> of the bug.
>

/************************************

Paul Flint
17 Averill Street
Barre, VT
05641

http://www.flint.com/home
skype: flintinfotech
Work: [phone]
  Fax: [phone]

Free advice .~.
is worth /V\
exactly what /( )\
you pay for it. ^^-^^

[Tammy Simpkins (tlsassoc)]

So, how does a user >Empty your trash and remove temporary packages of former installations using 'sudo apt-get clean'<? I have yet to locate this sudo apt-get clean, let alone use it, and since my problem began I've lost my audio, can't do any updates or upgrades. I know my hard drive has way more space available than the update manger alleges. so much for Ubuntu, Linux, firefox, or Mozilla or whatever you guys want to call it. I think we're going back to windows. At least their support isn't as hard to access. took me days to get to here, and I haven't seen anyone in the so-called "live chat" forum at all in three months that I've tried to get help.

[vlenk (vlenk)]

I had no problem upgrading from 9.04 to 9.10 on my desktop, allocating 40g of harddrive space.
:
However, I get the message "not enough disk space on / "when I try to upgrade 9.04 to 9.10 on my netbook, but I allocated 100g of harddrive space.

If there is any trash or temp packages, i didn't have time to create them, they came with the original 9.04 packages.

Yes I have tried sudo apt-get clean, to no avail.

[Erik Vandamme (erik1vandamme)]

I still have the same problem going from 9.04 to 9.10
In a 12GB root with 2.8GB free it requires 4200MB???
$ df -h /boot
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 12G 8.6G 2.8G 76% /

$ ls -lhA /boot
total 17M
-rw-r--r-- 1 root root 516K 2010-01-28 14:29 abi-2.6.28-18-generic
-rw-r--r-- 1 root root 95K 2010-01-28 14:29 config-2.6.28-18-generic
lrwxrwxrwx 1 root root 15 2010-02-15 21:18 debian.bmp -> /boot/sarge.bmp
drwxr-xr-x 2 root root 4.0K 2010-02-16 20:19 grub
-rw-r--r-- 1 root root 12M 2010-02-15 22:24 initrd.img-2.6.28-18-generic
-rw-r--r-- 1 root root 126K 2009-03-28 04:15 memtest86+.bin
-rw-r--r-- 1 root root 1.4M 2010-01-28 14:29 System.map-2.6.28-18-generic
-rw-r--r-- 1 root root 1.1K 2010-01-28 14:31 vmcoreinfo-2.6.28-18-generic
-rw-r--r-- 1 root root 3.4M 2010-01-28 14:29 vmlinuz-2.6.28-18-generic
erik@erik-i5:~$

[Jean-Baptiste Lallement (jibel)]

@Erik, vlenk, please attach the file /var/log/dist-upgrade/main.log from the time of the failure to this report.
Thanks.