rpm breaks own database again
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
RPM |
New
|
Undecided
|
Unassigned | ||
PLD Linux |
New
|
Undecided
|
Unassigned |
Bug Description
This is similar bug to closed one some time ago: https:/
-cut---
# poldek --noask --install-
[...]
Installing #305 package of total 420 (200.6M left to get)
Retrieving ftp://[...]/libgphoto
.......
Installing libgphoto2-
rpmdb: page 13: illegal page type or format
rpmdb: PANIC: Invalid argument
error: db4 error(-30974) from dbcursor->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) storing record libtool(
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting "libtool(
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting "libtool(
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting "libtool(
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting "libtool(
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting "libtool(
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting "libtool(
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting "libtool(
rpmdb: PANIC: fatal region error detected; run recovery
[...]
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting "libgphoto2" records from Providename index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db_create: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Conflictname index using db3 - (-30974)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db_create: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Dirnames index using db3 - (-30974)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db_create: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Requireversion index using db3 - (-30974)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db_create: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Provideversion index using db3 - (-30974)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db_create: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Installtid index using db3 - (-30974)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db_create: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Sigmd5 index using db3 - (-30974)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->cursor: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting "7c1a292cd9fd0c
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db_create: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Filemd5s index using db3 - (-30974)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
[...]
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: ftp://ftp.
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
[...]
rpmdb: File handles still open at environment close
rpmdb: Open file handle: /root/tmp/
rpmdb: Open file handle: /root/tmp/
rpmdb: Open file handle: /var/lib/
rpmdb: Open file handle: /root/tmp/
rpmdb: Open file handle: /root/tmp/
rpmdb: Open file handle: /var/lib/
rpmdb: Open file handle: /var/lib/rpm/Group
rpmdb: Open file handle: /var/lib/
rpmdb: Open file handle: /var/lib/
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
Installing #306 package of total 420 (199.4M left to get)
Retrieving ftp://ftp.
.......
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbenv->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: Runnning db->verify ...
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbenv->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: RUNRECOVERY failed, exiting ...
-cut---
Problem appeard some mounths ago. To reporduce You have to start instalation of hundreds of packages (>300). Bug apperars under i686 and x86_64 archs. Tested with db4.7 and db4.8.
# rpm -q poldek rpm db
poldek-
rpm-4.5-33.x86_64
Tested on count of machines (including virtual machines), this is not filesystem or hardware problem.