Red Hat Bugzilla – Bug 999591
yum tracebacks when updates repository is on a read-only filesystem
Last modified: 2013-09-12 04:37:01 EDT
Created attachment 788930 [details]
output of yum showing the traceback
Suppose I have a local mirror of the F19 updates mounted read-only via NFS, and a repo file that says:
name=Fedora $releasever - $basearch (mirror)
If I try to update from this, yum crashes with a traceback indicating that it was trying to unlink a drpm from the read-only filesystem. It shouldn't try to remove drpms from file-based repositories. (Arguably, it shouldn't bother with drpms at all on a file-based repository, or maybe that should be triggered on the "cost" value.)
Since it did actually build the package from the drpm, if I run it again (once for each rpm that needs to be constructed), it will eventually succeed.
yum version: yum-3.4.3-106.fc19.noarch
Thanks for the report! It's indeed a bug, but the fix is easy. I think presto plugin with keepdeltas=0 had the same bug.
> but the fix is easy
What is the fix?
I updated all my servers from F18 to F19 recently. Now I have this problem on all servers
# yum update
File "/usr/lib/python2.7/site-packages/yum/drpm.py", line 256, in _wait
OSError: [Errno 30] Read-only file system: '/repo/fedora-updates/19/x86_64/drpms/LibRaw-0.14.8-2.fc19_0.14.8-3.fc19.20120830git98d925.x86_64.drpm'
# rpm -q yum
In the pathname above /repo is read-only exported NFS filesystem.
It seems that this specific problem has been fixed in
But yum still handles local repositories badly as it rebuilds rpms from deltarpms (slow process that fills /var/yum/cache disk space). See https://bugzilla.redhat.com/show_bug.cgi?id=1007097