Red Hat Bugzilla – Bug 102223
RPM corrupts databases
Last modified: 2006-02-21 13:58:05 EST
Description of problem: rpm in beta corrupts databases just like RH9 did How reproducible: Use beta1, do lots of rpm updates error: db4 error(-30989) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found error: db4 error(-30989) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found
"corrupts" is the wrong word. rpm through Berkeley DB uses a db environment, DB_PAGE_NOTFOUND is an indication of cache incoherency, not "corruption". Workaround (until someone eventually gives me an angle on a reproducer, as I've never seen the problem) is to get rid of the cache rm -f /var/lib/rpm/__db* NEEDINFO looking for a an angle on a reproducer.
The rm doesnt work on the beta it seems. As for a reproducer - it has happened on every non i686 (smell a threading bug ??) beta install I have done.
Hmmm, not bug, but possibly (ahem) unrestrained configuration through anaconda. Might be angle here ... Jeremy: Can you reproduce this on non-ix86? If so, can you eyeball your (ahem) config speedups. And, at the minimum, can you nuke the __db* files at the end of an install?
we already do that: # rpm environment files go bye-bye for file in ["__db.001", "__db.002", "__db.003"]: try: os.unlink("%s/var/lib/rpm/%s" %(instPath, file)) except Exception, e: log("failed to unlink /var/lib/rpm/%s: %s" %(file,e))
So far so good in fedora 1 fingers crossed
*** This bug has been marked as a duplicate of 88720 ***
"So far so good in fc1" indicates something other than rpm code changes have improved the change, as ther have been no changes related to DB_PAGE_NOTFOUND that I know of. Keep crossing those fingers, mebbe it helps.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.