Not enough free disk space

Bug #95260 reported by Bert Vorenholt
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Jaunty by peterinmalaga

Bug Description

Binary package hint: update-manager

I Followed the steps described at http://wiki.kubuntu.org/KubuntuDistUpgrade
After automatically shutting down the update_manager, the upgradewizard takes over the process. after a few progress bars, I get a dialog that tells me the wizard will exit and i have to free at least 6 MB in the /boot partition, empty the trashcan and get rid of the cached packages with "apt-get clean". I emptied the trashes, cleaned the packages cache and have just one set of boot-files in /boot with 34 MB of free space on that particular partition.

Console messages from "kdesu update_manager":

kapture::PkgSystem::PkgSystem()
libasound2
libc6
mpg321
libasound2
libc6
mpg321
libasound2
libc6
mpg321
libasound2
libc6
mpg321
gpg: Signature made wo 14 mrt 2007 22:21:25 CET using DSA key ID 437D05B5
gpg: Good signature from "Ubuntu Archive Automatic Signing Key <email address hidden>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 6302 39CC 130E 1A7F D81A 27B1 4097 6EAF 437D 05B5
kdecore (KProcess): WARNING: setPty()
kdecore (KProcess): WARNING: _attachPty() 13
root@avkids-new:/home/bert# WARNING: Failed to read mirror file
Investigating libvolume-id0
Investigating debtags

Thanks in advance for your attention.

Bert Vorenholt
(The Netherlands ;-) )

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Please apply the files in /var/log/dist-upgrade

Thanks,
 Michael

Changed in update-manager:
status: Unconfirmed → Needs Info
Revision history for this message
glenner (glenner) wrote :

i am having a similar problem, the updater tells me to free at least 48.8M of space on /var/cache/apt/archives/ but according to df i have 1.2GB available on that partition.

/var/log/dist-upgrade/main.log contains:
(...)
2007-03-24 10:17:56,578 DEBUG Free space on /: 1232293888
2007-03-24 10:17:56,579 DEBUG Dir /usr mounted on /
2007-03-24 10:17:56,580 DEBUG Dir /var mounted on /
2007-03-24 10:17:56,581 DEBUG Dir /boot mounted on /
2007-03-24 10:17:56,582 DEBUG Dir /var/cache/apt/archives/ mounted on /
2007-03-24 10:17:56,583 DEBUG Free space on /home: 1611534336
2007-03-24 10:17:56,584 DEBUG fs_free contains: '{'/var': <DistUpgradeControler.FreeSpace object at 0x9b6a9c4c>, '/home': <DistUpgradeControler.FreeSpace object at 0x9b6a9b6c>, '/boot': <DistUpgradeControler.FreeSpace object at 0x9b6a9c4c>, '/usr': <DistUpgradeControler.FreeSpace object at 0x9b6a9c4c>, '/': <DistUpgradeControler.FreeSpace object at 0x9b6a9c4c>, '/var/cache/apt/archives/': <DistUpgradeControler.FreeSpace object at 0x9b6a9c4c>}'
2007-03-24 10:17:59,311 DEBUG dir '/var/cache/apt/archives/' needs '1281071154.0' of '<DistUpgradeControler.FreeSpace object at 0x9b6a9c4c>' (1232293888.000000)
2007-03-24 10:17:59,312 ERROR not enough free space on /var/cache/apt/archives/ (missing 48.8M)

the line
dir '/var/cache/apt/archives/' needs '1281071154.0'
makes me think the 44.4M displayed in the dialog is wrong and should be ~1280M ?

Revision history for this message
Bert Vorenholt (bert-vorenholt-nl) wrote :

Thanks for your quick responce!

Revision history for this message
Bert Vorenholt (bert-vorenholt-nl) wrote :

Thanks for your quick response!

Revision history for this message
Bert Vorenholt (bert-vorenholt-nl) wrote :

As i reed the main.log it seems the upgrade needs 40 MB free space on the /boot partition. My /boot partition is just 49,4 MB and contains the files for just one kernel.
Do i really need to repartition?

Thanks for your interest,
Bert

Revision history for this message
Bert Vorenholt (bert-vorenholt-nl) wrote :

I'll answer my own question here :-)

>> Do i really need to repartition?

Yes.

After i have grown my /boot partition to have the desired free space, the upgrade went well for me :-)

Strange though, now with two kernels in my /boot folder/partition, the used space is around 20 MB.
Why the upgrade needs 40 MB free space in /boot?

Thanks.
Bert

Revision history for this message
Boerdy (boerdy-deactivatedaccount) wrote :

I have exactly the same problem like Bert Vorenholt.
Tried "sudo update-manager -d". After a while i get this message:

"Not enough free disk space

The upgrade aborts now. Please free at least 6671k of disk space on /boot. Empty your trash and remove temporary packages of former installations using 'sudo apt-get clean'."

Output of 'df -h /boot/':
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 45M 8.1M 34M 20% /boot

Seems like the upgrade process needs 40MB of free space on /boot (34 are available plus 6 needed)...

Thanks
Boerdy

Revision history for this message
Christopher Houdeshell (choudeshell) wrote :

Confirmed.

Changed in update-manager:
assignee: nobody → choudesh
status: Needs Info → Confirmed
assignee: choudesh → nobody
Revision history for this message
Christopher Houdeshell (choudeshell) wrote :

2007-04-11 20:04:30,462 DEBUG Free space on /: 1117741056
2007-04-11 20:04:30,462 DEBUG Dir /usr mounted on /
2007-04-11 20:04:30,462 DEBUG Dir /var mounted on /
2007-04-11 20:04:30,462 DEBUG Free space on /boot: 53260288
2007-04-11 20:04:30,463 DEBUG Dir /var/cache/apt/archives/ mounted on /
2007-04-11 20:04:30,463 DEBUG Free space on /home: 6449012736
2007-04-11 20:04:30,463 DEBUG fs_free contains: '{'/var': <DistUpgradeControler.FreeSpace object at 0xb3471bac>, '/home': <DistUpgradeControler.FreeSpace object at 0xb3471c2c>, '/boot': <DistUpgradeControler.FreeSpace object at 0xb3471c0c>, '/usr': <DistUpgradeControler.FreeSpace object at 0xb3471bac>, '/': <DistUpgradeControler.FreeSpace object at 0xb3471bac>, '/var/cache/apt/archives/': <DistUpgradeControler.FreeSpace object at 0xb3471bac>}'
2007-04-11 20:04:30,833 DEBUG dir '/var/cache/apt/archives/' needs '1241222620.0' of '<DistUpgradeControler.FreeSpace object at 0xb3471bac>' (1117741056.000000)
2007-04-11 20:04:30,834 ERROR not enough free space on /var/cache/apt/archives/ (missing 123M)

Seems edgy->feisty needs an [insane] amount of diskspace.

Revision history for this message
Michael Vogt (mvo) wrote :

@CHoudeshell: It seems to require '1.2G' of debs. That is a pretty big amount, can you please attach your complete main.log file? If you have a lot of packages installed, that is not a unreasonable amount, but its pretty big.

Revision history for this message
ramonono (ramonono) wrote :

I got this error (no space in /boot) upgrading from 7.04 to 7.10

The problem I see is that I never touched whatever it is in /boot since I created it in a previous ubuntu installation (245MiB), so I think that the update manager should know how to make the space needed (deleting the oldest files until it's satisfied for example).

I tried to resize the partition, but gparted won't allow me to do that. I think it's because the main ubuntu filesystem was created as lvm and is shown as unknown filesystem. My fault, but don't ask me why, it was about 5.10 and I can't barely rembember it now :-/

Revision history for this message
Matthew Craig (matthew-t-craig) wrote :

Had this same problem with the Feisty -> Gutsy upgrade.

A Little Rant:
Update-manager should have determined there was insufficient space before starting the download!! Before it did anything else!! Instead, the upgrade critically failed mid-way through configuring all system files!!

Troubleshooting Details:
Used the Feisty LiveCD to run "gparted" and resize the /boot partition, but update-manager left the OS in such a bad state that any kernel that I tried to boot only arrived at a "BusyBox" prompt. Since grub seemed to be finding to the /boot partition correctly, but the system was not working, my next step was a complete re-install of Feisty and a new upgrade to Gutsy. This re-install and clean upgrade ultimately worked, especially now that the /boot partition is 3x the size, but I lost all of my installed applications.

More thoughts:
I think the most important thing with this bug is that it could have been prevented by checking for disk space pre-requisites. Seems like a prudent task, especially as the kernel is being modified and the system is then being rebooted, at the completion of the process.

Changed in update-manager:
status: Confirmed → Invalid
Revision history for this message
markling (markling) wrote :
Download full text (5.4 KiB)

I've got this problem with Xubuntu 12.10.

It is a fault with the Ubuntu Software Updater.

It is also a fault with the installer.

My machine was a clean install six months ago. I did a guided, encrypted LVM. I used a boot partition of the recommended size. Now six months later Xubuntu's telling me on the hand I need to upgrade my kernel, and on the other that I can't upgrade my kernel because there is not enough space in my boot partition.

There are two problems here:

i) the standard setting wasn't big enough to see my machine even through its first upgrade

ii) my /boot partition is being over-filled with trash that is nothing to do with me as a user. I shouldn't have to know about this. This problem should not effect me.

Notably, this was the first time I opted to have a separate partition for my home directory. All over Ubuntu installs since 2008, on a variety of machines, have been on a single partition. The problem never occurred before in any of these instances.

It would be most helpful if the following solutions were given serious consideration:

i) The ubuntu/xubuntu installer needs to create a boot partition of the appropriate size. It should inform a user who tries to create a /boot partition that is too small.

ii) The Software Center should clean up its trash. It is most unhygenic of it to simply discard unused kernel images in the /boot directory. If it is the case that expert users like to keep old kernels hanging around, then the default should favour non-expert users by having them removed automatically. Perhaps the option could be flagged on the instance of a kernel upgrade.

Here's my situation:

~$ sudo df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/xubuntu-root 143G 62G 75G 45% /
udev 1.7G 4.0K 1.7G 1% /dev
tmpfs 702M 820K 701M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 1.8G 80K 1.8G 1% /run/shm
none 100M 20K 100M 1% /run/user
/dev/sda1 228M 193M 24M 90% /boot

Current kernel: Linux 3.5.0-27-generic UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

~$ ls -l /boot
total 192736
-rw-r--r-- 1 root root 848290 Jan 8 22:09 abi-3.5.0-22-generic
-rw-r--r-- 1 root root 848290 Jan 24 13:38 abi-3.5.0-23-generic
-rw-r--r-- 1 root root 849836 Feb 7 02:13 abi-3.5.0-24-generic
-rw-r--r-- 1 root root 849836 Feb 25 18:49 abi-3.5.0-25-generic
-rw-r--r-- 1 root root 850088 Mar 8 23:41 abi-3.5.0-26-generic
-rw-r--r-- 1 root root 852365 Mar 25 20:20 abi-3.5.0-27-generic
-rw-r--r-- 1 root root 147871 Jan 8 22:09 config-3.5.0-22-generic
-rw-r--r-- 1 root root 147871 Jan 24 13:38 config-3.5.0-23-generic
-rw-r--r-- 1 root root 147944 Feb 7 02:13 config-3.5.0-24-generic
-rw-r--r-- 1 root root 147944 Feb 25 18:49 config-3.5.0-25-generic
-rw-r--r-- 1 root root 147944 Mar 8 23:41 config-3.5.0-26-generic
-rw-r--r-- 1 root root 148096 Mar 25 20:20 config-3.5.0-27-generic
drwxr-xr-x 5 root root 1024 Apr 30 21:25 grub
-rw-r--r-- 1 root root 23633726 Jan 19 08:33 initrd.img-3.5.0-22-generic
-rw-r--r-- 1 root root 23635169 Feb 1 12:16 initrd...

Read more...

Changed in update-manager (Ubuntu):
status: Invalid → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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