[Rpm-maint] [rpm-software-management/rpm] Rpm query causes corruption in the file-backed mmaped bdb regions (#232)

Jeff Johnson notifications at github.com
Sat Jun 10 15:59:16 UTC 2017

Note also that simply removing __db.00N files to "fix" problems can lead to other "corruption" problems, particularly when other accesses are running simultaneously.

The better fix for what you are calling "corruption" is to use "db_recover" with/without the -e option.

BDB has a notification facility that db_recover will use to signal other processes that the dbenv is being recreated. But (last I checked) rpm-4.x.y does not use/implement that facility. RPM5+BDB does implement the dbenv notification facility, automates recovery where needed on the next dbenv open, and also uses a full transactional ACID store with logs, rpm-4.x.y uses a CDB model which permits a single writer or multiple readers, with per-database (i.e. per-table) locking. The transactional model uses per-page locking, and logs all operations with a transactional commit/discard operation. 

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20170610/a1cc80a6/attachment.html>

More information about the Rpm-maint mailing list