errors report by update manager

Asked by Abe

During installing updates on Ubuntu 12.04 LTS from Linux u 3.2.0-75 to Linux u 3.2.0-76 via Package Manager I got an error stating that the package system was broken. The problem seems related to not having enough disk space. However, it looks to me there was plenty of space left on the disk. At this point I have already deleted previous linux (u 3.2.0-75). I would like to know how to fix it, if there is any. I appreciate your helps. Thanks.

Below were errors from the package manager:

me@u:~$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  lib32gcc1 lib32asound2 lib32stdc++6
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
The following NEW packages will be installed:
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
3 not fully installed or removed.
Need to get 0 B/11.7 MB of archives.
After this operation, 56.4 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
(Reading database ... 1057780 files and directories currently installed.)
Unpacking linux-headers-3.2.0-76 (from .../linux-headers-3.2.0-76_3.2.0-76.111_all.deb) ...
dpkg: error processing /var/cache/apt/archives/linux-headers-3.2.0-76_3.2.0-76.111_all.deb (--unpack):
 unable to create `/usr/src/linux-headers-3.2.0-76/include/linux/ultrasound.h.dpkg-new' (while processing `./usr/src/linux-headers-3.2.0-76/include/linux/ultrasound.h'): No space left on device
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)

Below are disk space usage info from my system:

me@u:~$ df -Tih
Filesystem Type Inodes IUsed IFree IUse% Mounted on
/dev/sda11 ext4 2.0M 148K 1.8M 8% /
udev devtmpfs 493K 492 492K 1% /dev
tmpfs tmpfs 495K 439 494K 1% /run
none tmpfs 495K 3 495K 1% /run/lock
none tmpfs 495K 7 495K 1% /run/shm
/dev/sda9 ext4 299K 36 299K 1% /tmp
/dev/sda1 ext4 36K 232 36K 1% /boot
/dev/sda5 ext4 895K 23K 872K 3% /home
/dev/sda7 ext4 895K 893K 2.0K 100% /usr
/dev/sda8 ext4 597K 21K 576K 4% /var
/dev/sda6 ext4 1.5M 29K 1.5M 2% /usr/local
/dev/sr0 iso9660 0 0 0 - /media/VBOXADDITIONS_4.3.20_96996

me@u:~$ df -Th
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda11 ext4 31G 5.4G 24G 19% /
udev devtmpfs 2.0G 4.0K 2.0G 1% /dev
tmpfs tmpfs 396M 1.0M 395M 1% /run
none tmpfs 5.0M 0 5.0M 0% /run/lock
none tmpfs 2.0G 200K 2.0G 1% /run/shm
/dev/sda9 ext4 4.6G 138M 4.3G 4% /tmp
/dev/sda1 ext4 138M 32M 99M 25% /boot
/dev/sda5 ext4 14G 923M 13G 7% /home
/dev/sda7 ext4 14G 6.4G 6.8G 49% /usr
/dev/sda8 ext4 9.2G 996M 7.8G 12% /var
/dev/sda6 ext4 23G 2.5G 20G 12% /usr/local
/dev/sr0 iso9660 56M 56M 0 100% /media/VBOXADDITIONS_4.3.20_96996

Question information

English Edit question
Ubuntu util-linux Edit question
No assignee Edit question
Solved by:
Last query:
Last reply:
Revision history for this message
Abe (urland-b) said :

I found the answer to my problem. My problem is the same as stated in the link below. It appeared that many inodes in /usr were not cleaned up from previous updates. Once I cleaned them up, I was able to continue update. Thanks.