Re: FW: upgrade problem
On 6 February 2014 08:31, Roelof Wobben <rwobben@hotmail.com> wrote:
>> ----------------------------------------
>>> Date: Wed, 5 Feb 2014 16:35:47 -0500
>>> From: debian@paulscrap.com
>>> To: debian-user@lists.debian.org
>>> Subject: Re: upgrade problem
>>>
>>>
>>>
>>> On 02/05/2014 04:16 PM, Roelof Wobben wrote:
>>>> When I did today apt-get dist-upgrade it fails with this message :
>>>>
>>>> Preconfiguring packages ...
>>>> (Reading database ... 146026 files and directories currently installed.)
>>>> Preparing to unpack .../linux-image-3.12-1-amd64_3.12.9-1_amd64.deb ...
>>>> Unpacking linux-image-3.12-1-amd64 (3.12.9-1) over (3.12.6-2) ...
>>>> dpkg: error processing archive /var/cache/apt/archives/linux-image-3.12-1-amd64_3.12.9-1_amd64.deb (--unpack):
>>>> cannot copy extracted data for './lib/modules/3.12-1-amd64/kernel/net/l2tp/l2tp_ip6.ko' to '/lib/modules/3.12-1-amd64/kernel/net/l2tp/l2tp_ip6.ko.dpkg-new': failed to write (No space left on device)
>>>> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
>>>> Errors were encountered while processing:
>>>> /var/cache/apt/archives/linux-image-3.12-1-amd64_3.12.9-1_amd64.deb
>>>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>>>
>>>>
>>>> but df -i schows there is enough room :
>>>>
>>>> Bestandssysteem I-nodes IGebr IVrij IGeb% Aangekoppeld op
>>>> /dev/sda1 85344 7496 77848 9% /
>>>> udev 505442 497 504945 1% /dev
>>>> tmpfs 507394 562 506832 1% /run
>>>> tmpfs 507394 1 507393 1% /run/lock
>>>> tmpfs 507394 9 507385 1% /run/shm
>>>> /dev/sda9 3727360 13188 3714172 1% /home
>>>> /dev/sda8 97536 23 97513 1% /tmp
>>>> /dev/sda5 549440 143994 405446 27% /usr
>>>> /dev/sda6 183264 9332 173932 6% /var
>>>> none 507394 2 507392 1% /sys/fs/cgroup
>>>>
>>>>
>>>> Roelof
>>>>
>>>
>>> What about df -h (or just plain df if you prefer)? It's entirely
>>> possible to fill up a drive an still have inodes left.
>>>
>>> - PaulNM
>
>
> df -h gives this :
>
> /dev/sda1 315M 210M 85M 72% /
> udev 10M 0 10M 0% /dev
> tmpfs 397M 784K 396M 1% /run
> tmpfs 5,0M 0 5,0M 0% /run/lock
> tmpfs 2,4G 88K 2,4G 1% /run/shm
> /dev/sda9 56G 460M 53G 1% /home
> /dev/sda8 360M 2,1M 335M 1% /tmp
> /dev/sda5 8,2G 3,4G 4,3G 45% /usr
> /dev/sda6 2,7G 633M 2,0G 25% /var
> none 4,0K 0 4,0K 0% /sys/fs/cgroup
>
> df gives this :
>
> /dev/sda1 322023 214592 86286 72% /
> udev 10240 0 10240 0% /dev
> tmpfs 405916 784 405132 1% /run
> tmpfs 5120 0 5120 0% /run/lock
> tmpfs 2488920 92 2488828 1% /run/shm
> /dev/sda9 58512580 467768 55049460 1% /home
> /dev/sda8 368615 2070 342993 1% /tmp
> /dev/sda5 8518920 3558876 4504264 45% /usr
> /dev/sda6 2817056 647952 2006288 25% /var
> none 4 0 4 0% /sys/fs/cgroup
>
> Roelof
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: DUB121-W10D41B9A6A3ABFD5FEF060AE940@phx.gbl">http://lists.debian.org/DUB121-W10D41B9A6A3ABFD5FEF060AE940@phx.gbl
>
I don't know the inner workings of dpkg. But during the extraction
process does dpkg use the /tmp partition?
The /tmp partition is 360MB. Maybe increasing /tmp size or setting up
/tmp on home may help
--
rob
Reply to: