Hide Forgot
Description of problem: I´ve tried to run a software update. Yum recognised a problem and I get this stacktrace: Traceback (most recent call last): File "/usr/share/PackageKit/helpers/yum/yumBackend.py", line 2426, in _runYumTransaction rpmDisplay=rpmDisplay) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 4511, in processTransaction self._doTransaction(callback,display=rpmDisplay) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 4625, in _doTransaction self.runTransaction( cb=cb ) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1405, in runTransaction self.verifyTransaction(resultobject) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1507, in verifyTransaction self.history.end(self.rpmdb.simpleVersion(main_only=True)[0], ret) File "/usr/lib/python2.7/site-packages/yum/rpmsack.py", line 965, in simpleVersion if 'checksum_type' in ydbi and 'checksum_data' in ydbi: File "/usr/lib/python2.7/site-packages/yum/rpmsack.py", line 1672, in __contains__ x = self.get(attr) File "/usr/lib/python2.7/site-packages/yum/rpmsack.py", line 1702, in get res = self._read(attr) File "/usr/lib/python2.7/site-packages/yum/rpmsack.py", line 1619, in _read info = misc.stat_f(fn) File "/usr/lib/python2.7/site-packages/yum/misc.py", line 907, in stat_f return os.stat(filename) OSError: [Errno 20] Not a directory: '/var/lib/yum/yumdb/P/d5bae7e6f8f7e72f9b8c7c5c085b7119a596c8f2-PackageKit-glib-0.6.12-3.fc14-i686/checksum_type' Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Hi! Thanks for the report. Is it reproducible? Do you get the same backtrace if you run the update again? Also, could you run: $ stat /var/lib/yum/yumdb/P/d5bae7e6f8f7e72f9b8c7c5c085b7119a596c8f2-PackageKit-glib-0.6.12-3.fc14-i686 (should be a directory, but the backtrace suggests it's a file).
Ye,it is reproducible, and yes it is the same backtrace(as far as I remember). For the rest give me some time. It is mot my working setup, but I have the machine around here.
Ahh, forget it. I´ve just started the machine which brought up a harddisk/filesystem error(multiple use of the same blocks), so that could be the cause or the consequence of the failed update. The system is not startable, so... I can not provide more information as you already have. Good luck.
The update has failed because of corrupted FS. Yumdb touches a lot of files so it's hit quickly. You may try booting single or from different media, and running fsck manually.