Re: dpkg: error,processing /var/cache/apt/archives/ia32-libs-gtk_2.5_amd64.deb,(--unpack):



On 2008-07-05 07:49 +0200, gary turner wrote:

(Reading database ... 85648 files and directories currently installed.)
Unpacking ia32-libs-gtk (from .../ia32-libs-gtk_2.5_amd64.deb) ...
dpkg: error
processing /var/cache/apt/archives/ia32-libs-gtk_2.5_amd64.deb
(--unpack):
failed in buffer_write(fd) (10, ret=-1): backend dpkg-deb during
`./emul/ia32-linux/usr/lib/libQtCore.so.4.4.0': No space left on device

If the "No space left on device" means what I think it does, I'm
confused. This is a new install with lots of room on the disk. 2.1GB
used in /usr, and 407MB in /var

Learn reading. ;-) The offending file lives is in /emul, i.e. on the
root partition, not in /usr.

aretha:/home/gt# fdisk -l

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x20000000

Device Boot Start End Blocks Id System
/dev/sda1 * 1 31 248976 83 Linux
/dev/sda2 32 274 1951897+ 82 Linux swap /
Solaris
/dev/sda3 275 1490 9767520 83 Linux
/dev/sda4 1491 37477 289065577+ 5 Extended
/dev/sda5 1491 2706 9767488+ 83 Linux
/dev/sda6 2707 6353 29294496 83 Linux
/dev/sda7 6354 37477 250003498+ 83 Linux

aretha:/home/gt# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/sda1 / ext3 errors=remount-ro 0 1
/dev/sda7 /home ext3 defaults 0 2
/dev/sda6 /opt ext3 defaults 0 2
/dev/sda3 /usr ext3 defaults 0 2
/dev/sda5 /var ext3 defaults 0 2
/dev/sda2 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0

So you have less than 250 Megabyte for the root partition. With today's
big kernels that is pretty tight.

The question is how do I clean up the mess? Right now, I'm unable to
remove or install anything (apt) as any attempt recalls this error.
I'm not averse to simply re-installing the dist, but would rather know
how I got into the mess in the first place, and what to do about it.

Try to remove old kernels, that should give you back some space. But in
the long run you may need to increase the root filesystem to prevent the
error from reoccuring.

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx



Relevant Pages

  • Re: Installation of hard drive
    ... Tell us which is the file systems that you have used on new disk partitions. ... Windows should be cleared, but how thee partition ... Where did you install ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: Installation of hard drive
    ... Tell us which is the file systems that you have used on new disk partitions. ... Where did you install ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: Installing on a small root partition
    ... I have had cases with repeated reboots, ... I am trying to do a specialized install of Debian. ... my plan is to have a small root partition (say about ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: The Final Frontier. Upgrading Sarge to Etch
    ... original disk intact. ... The test was what would happen if I just ran the upgrade and see ... Instead of investigating the install failure further, ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • RE: Problem With Disk2
    ... I was wanting to test an install for compatibility ... I have seen a similar problem when using Vmware, is this were you are seeing ... but the second disk always failes. ... unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe ...
    (RedHat)