FS#6716 - Pacman 3.0 thinks i have run out of disk space

Attached to Project: Pacman
Opened by Oscar (borkdox) - Tuesday, 27 March 2007, 01:02 GMT
Task Type Bug Report
Category
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I just did a pacman -Su inside my 32-bit chroot on my arch64 box. Now Pacman is shot, and cannot install or upgrade any package because it thinks i have run out of diskspace which clearly I have not (30 gigs free). I am guessing it is because the way things are mounted inside the chroot pacman cannot properly detect freespace...

Here is pacman's output:

[root@arch64box /]# pacman -U /var/cache/pacman/pkg/wine-0.9.29-1.pkg.tar.gz
loading package data... done.
checking dependencies... done.
cleaning up... done.
(1/1) checking for file conflicts [#####################] 100%
error: failed to prepare transaction (not enough space on disk)
:: 11.6 MB required, have 0.0 MB

if any other info could be helpful let me know...
This task depends upon

Closed by  Aaron Griffin (phrakture)
Friday, 30 March 2007, 04:47 GMT
Reason for closing:  Fixed
Additional comments about closing:  code in CVS now spits out a proper error message, but keeps the failure, as it is an important one.
Comment by Aaron Griffin (phrakture) - Tuesday, 27 March 2007, 03:32 GMT
Can you provide "df -h" output inside the chroot?
Comment by Aaron Griffin (phrakture) - Tuesday, 27 March 2007, 05:59 GMT
Here's one thing to consider. The freespace checking routines actually read volume information from mtab to know what is mounted. Could you try, maybe, copying /etc/mtab to the chroot before chrooting?
Comment by Jan de Groot (JGC) - Tuesday, 27 March 2007, 06:14 GMT
ln -sf /proc/mounts /etc/mtab works out in my chroots.
Comment by Oscar (borkdox) - Tuesday, 27 March 2007, 15:17 GMT
the problem was, as some of you pointed out above, that mtab was empty inside the chroot. Pacman 2 did not have this problem, so im guessing Pacman 3 has a new "feature" that uses mtab to determine the volume's to check for freespace.

This bug can be closed if pacman 3 in fact has this new "feature".
Comment by Jan de Groot (JGC) - Tuesday, 27 March 2007, 15:36 GMT
pacman3 uses either /etc/mtab or the mount output to determine the filesystem that would be affected by the package upgrade/installation. If there's not enough space on this volume, pacman will abort the installation with your errormessage.

IMHO pacman should give a warning when it fails to retrieve a partition/mountpoint for this and just continue installation after an optional confirmation.
Comment by Aaron Griffin (phrakture) - Tuesday, 27 March 2007, 16:23 GMT
I agree, adding a warning that mtab couldn't be opened is ideal.

Loading...