FS#44942 - Pacman miserably handles ENOSPC

Attached to Project: Pacman
Opened by Alexandre Bique (babali) - Tuesday, 12 May 2015, 09:51 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 12 May 2015, 17:46 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Hi,

It seems that pacman do not handle well a full disk.
A friend did install go from pacman, and the installation went wrong with tons of errors like:

error: could not extract usr/lib/go/src/go/doc/testdata/error2.2.golden (Write to restore size failed)

And then pacman considered go successfully installed but it was not! She had to remove go with pacman -R and then cleanup the files by hand on the disk to really uninstall go.

Thanks for having a look!
This task depends upon

Closed by  Dave Reisner (falconindy)
Tuesday, 12 May 2015, 17:46 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#37402 
Comment by Alexandre Bique (babali) - Tuesday, 12 May 2015, 09:55 GMT
She's running the OS in VirtualBox, the virtual size of the FS is 10G, but once she reached 8G her windows disk was full and VirtualBox could not extend the disk and satisfy the "virtual size". So the linux kernel probably got a write error on the disk.
Comment by Alexandre Bique (babali) - Tuesday, 12 May 2015, 09:58 GMT
Oups sorry, I said something wrong. There was space on the windows filesystem, but the linux one got full.
Comment by Allan McRae (Allan) - Tuesday, 12 May 2015, 12:05 GMT
Did VirtualBox expand the filesystem to 10G or not?
What filesystem was the install using?
Was the CheckSpace option enabled in pacman.conf?
Comment by Alexandre Bique (babali) - Tuesday, 12 May 2015, 16:42 GMT
I can't check right now, but if I'm right she's on btrfs and her linux partition was full.
Sorry it is not very detailed :/
If there are not enough information to start checking some execution path, then we can close the bug.

Thanks!

Loading...