You are not logged in.
Pages: 1
I was upgrading a package the other day with pacman and it was short of disk space on the partition space it was going on (/opt) and even though the check is turned on, it was trying to still overrun. It just came back with error message about not being able to write the files that were due to out of disk space. I've of course since resized that partition. Was happy to notice that pacman did report a corrupted package and which one it was I was reusing, which was not there before.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
I'm sorry, I don't understand what the problem is.
If there's a questions / issue in there, can you rephrase it?
Offline
I thought the disk space check on pacman was to prevent installing packages that would go past disk space limits, if found before installing them. It seemed to be trying to install in spite of this check. I was thinking that an error message should've come up to state that pacman is not installing the package due to the fact that disk space is too low for the package. It is possible that if the package is being installed over multiple partitions, the install calculation changes. Even though I've done a pacman --debug before, it seems to check the different filesystems to check each one.
The message I was getting was:
error: could not extract <file> (Write failed)
Where I was thinking pacman would've done its' disk check and stated something like:
error: one or more packages will exceed disk space constraints
It's not serious, but may be a suprise when disk space is low.
Last edited by nomorewindows (2012-07-24 02:56:57)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
If you think this is a bug, please file a report at bugs.archlinux.org
ᶘ ᵒᴥᵒᶅ
Offline
Hmm... disc space is calculated on a per partition basis and has a reasonable buffer built in so this should not happen. Of course, you can fool it by having something write a lot to the partition between when the check is done and when the install is done.
What type of filesystem is the partition that got fulled?
Offline
I've resized it and some other partitions but I think it was ext3.
/opt is pretty inactive, so it wasn't writing anything.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Pages: 1