Need better handling of no space left rpm errors
Bug #635854 reported by
Jeff Johnson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
RPM |
Triaged
|
Low
|
Unassigned | ||
Fedora |
Invalid
|
Medium
|
Bug Description
tracker
tags: | added: diskspace fedora |
Changed in rpm: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: errors |
Changed in fedora: | |
importance: | Unknown → Medium |
status: | Unknown → Invalid |
To post a comment you must log in.
Description of problem:
A couple times recently during updates I've run out of space:
Error unpacking rpm package 1:openoffice. org-core- 3.0.1-15. 1.fc10. i386 openoffice. org/basis3. 0/program/ libbf_svxli. so;496f2290: cpio: write failed - No space left on device 1.1.12- 1.fc10. i386 wine/credui. dll.so; 496f2290: cpio: write failed - No space left on device
error: unpacking of archive failed on file /usr/lib/
Error unpacking rpm package wine-core-
error: unpacking of archive failed on file /usr/lib/
....
and so on.
Now, it appears that yum (and perhaps rpm?) believes than nothing went wrong:
There were non-fatal errors in the transaction
But many (most?) of the packages for which there are errors are then no longer in the rpm database.
Version-Release number of selected component (if applicable): 21-2.fc10. noarch 0-0.rc3. 1.fc10. i386
yum-3.2.
rpm-4.6.