Re: dpkg: error,processing /var/cache/apt/archives/ia32-libs-gtk_2.5_amd64.deb,(--unpack):
Sven Joachim wrote:
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) ...
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.
I was fooled by the ./, assuming (wrongly, it seems) that the current
directory was /var or possibly /usr. This is my first look at a 64bit
machine, and was not ready for a 32bit emulation under /.
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
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
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?
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.
Repartitioning, and giving / a GB seems to have done the job. Thanks
for pointing out the /emul directory. It's one I was completely unaware of.
Anyone can make a usable web site. It takes a graphic
designer to make it slow, confusing and painful to use.
org:Gary Turner, Web Developer