Bug 682509

Summary: [abrt] yum-3.2.28-5.fc13: rpmsack.py:38:<module>:ValueError: bad marshal data
Product: [Fedora] Fedora Reporter: Roman Melihhov <roman>
Component: yumAssignee: Seth Vidal <skvidal>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: ffesti, james.antill, maxamillion, pmatilai, tla
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:21699a00
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-07 20:22:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Roman Melihhov 2011-03-06 09:54:55 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/yum
component: yum
executable: /usr/bin/yum
kernel: 2.6.33.3-85.fc13.x86_64
package: yum-3.2.28-5.fc13
reason: rpmsack.py:38:<module>:ValueError: bad marshal data
release: Fedora release 13 (Goddard)
time: 1299405208
uid: 500

How to reproduce
-----
1. running yum
2.
3.
Comment 1 Roman Melihhov 2011-03-06 09:55:10 UTC 
Created attachment 482500 [details]
File: backtrace
Comment 2 Roman Melihhov 2011-03-07 20:22:35 UTC 
Errpor fixed. It appears that due to some errors on some mounted filesystems there were IO error. Error fixed by forcing fsck.

su touch /forcefsck

and rebooted machine.

I hope this helps others too