pacman -U reports package needing a crazy number of blocks

ninian · 2012-08-06 15:34:38

I'm testing a package provided by a reliable 3rd party and it fails to install on one system, but succeeds on another (both 32-bit systems). On the failing installation, pacman reports that the package requires a crazily huge number of blocks:

# pacman -U <package>
loading packages...
resolving dependencies...
looking for inter-conflicts...

Targets (1): <package>

Total Installed Size:   6.54 MiB
Net Upgrade Size:       0.02 MiB

Proceed with installation? [Y/n] 
(1/1) checking package integrity                                   [####################################] 100%
(1/1) loading package files                                        [####################################] 100%
(1/1) checking for file conflicts                                  [####################################] 100%
(1/1) checking available disk space                                [####################################] 100%
error: Partition / too full: 2552376766501889 blocks needed, 2089921 blocks free
error: not enough free disk space
error: failed to commit transaction (not enough free disk space)
Errors occurred, no packages were upgraded.

Running pacman -U --debug shows (snipped):

debug: partition /, needed 2552325226889216, cushion 5121, free 2090145
error: Partition / too full: 2552325226894337 blocks needed, 2090145 blocks free
debug: returning error 7 from _alpm_check_diskspace : not enough free disk space

I can install other packages with pacman fine and have never encountered this problem before. My root filesystem is not full:

# df
Filesystem     1K-blocks     Used Available Use% Mounted on
rootfs          25761332 17398388   7052040  72% /
dev               509384        0    509384   0% /dev
run               511272      572    510700   1% /run
/dev/sda2       25761332 17398388   7052040  72% /
tmpfs             511272      132    511140   1% /dev/shm
tmpfs             511272        0    511272   0% /sys/fs/cgroup
tmpfs             511272       44    511228   1% /tmp

namcap showed nothing unusual about the package (which is not open source), and checks on my hard drive show nothing amiss.
Would be grateful for any pointers to solve this unusual problem!

Leonid.I · 2012-08-06 17:43:13

Can you actually extract the package and measure the occupied disk space? Also what does pacman -Qpi <package> say?

ninian · 2012-08-06 18:30:01

Leonid.I wrote:

Can you actually extract the package and measure the occupied disk space? Also what does pacman -Qpi <package> say?

Yes - extracted it to a temporary directory and it occupied 6.2M of disk space, according to the du -h command. Directories and files looked fine.
pacman -Qpi =>

Compressed Size: 2485.82 KiB
Installed Size : 6692.00 KiB

All seems reasonable, but .... !
(Also re-archived all the extracted stuff into a .pkg.tar.xz archive and got the same problem.)

Edit: But both the .tar.gz and .tar.xz packages install without error on a second system, upgraded with pacman -Syu today to exactly the same level as the first system!

Last edited by ninian (2012-08-06 18:34:05)

Allan · 2012-08-06 21:21:36

What filesystem is /?

ninian · 2012-08-06 21:29:16

Allan wrote:

What filesystem is /?

On both systems, it's ext3.
By the way, I noticed that the package was made with rather outdated versions; here's what it says in .PKGINFO:

# Generated by makepkg 3.3.3
# using fakeroot version 1.14.4

Of significance I wonder?

Edit: If I comment out the 'CheckSpace' option in /etc/pacman.conf, the package installs fine.

Last edited by ninian (2012-08-06 22:09:45)

Lennie · 2012-08-07 05:49:38

I have also encountered this strange problem, with an AUR-package. Everything ninian has said is the same for me, except I have Ext4. It's my computer at work. I'll give it another try when I come to work (if I don't forget about it again...)

Leonid.I · 2012-08-09 00:17:58

Lennie wrote:

I have also encountered this strange problem, with an AUR-package. Everything ninian has said is the same for me, except I have Ext4. It's my computer at work. I'll give it another try when I come to work (if I don't forget about it again...)

What package is that?

Lennie · 2012-08-09 05:44:35

I'm not at work now so I can't check right now, but I think it must be foomatic-db-foo2zjs. It's a dependency for foo2zjs, and the strange thing is, I use packer as aur-helper and it can handle dependencies, but not for this package. So I several times tried to run 'packer -Syu --auronly' and then it tried to build foo2zjs before foomatic-db-foo2zjs, but it didn't build it because of missing dependency. And then this strange error about size when it tried to install foomatic-db-foo2zjs. But no error when it was build what I could see. I temporarely commented out CheckSpace in pacman.conf to install it.

Arch Linux

#1 2012-08-06 15:34:38

pacman -U reports package needing a crazy number of blocks

#2 2012-08-06 17:43:13

Re: pacman -U reports package needing a crazy number of blocks

#3 2012-08-06 18:30:01

Re: pacman -U reports package needing a crazy number of blocks

#4 2012-08-06 21:21:36

Re: pacman -U reports package needing a crazy number of blocks

#5 2012-08-06 21:29:16

Re: pacman -U reports package needing a crazy number of blocks

#6 2012-08-07 05:49:38

Re: pacman -U reports package needing a crazy number of blocks

#7 2012-08-09 00:17:58

Re: pacman -U reports package needing a crazy number of blocks

#8 2012-08-09 05:44:35

Re: pacman -U reports package needing a crazy number of blocks

Board footer