[Bug 574002] Re: rpm breaks own database again

[Jeff Johnson]

** Also affects: rpm
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are subscribed to PLD
Linux.
https://bugs.launchpad.net/bugs/574002

Title:
  rpm breaks own database again

Status in rpm package manager:
  New
Status in PLD Linux Distribution:
  New

Bug description:
  This is similar bug to closed one some time ago:
  https://bugs.launchpad.net/pld-linux/+bug/389983 but apears in rpm 4.7

  -cut-------------------------------------------------
  # poldek --noask --install-dist=/root/tmp/testrpm/ FHS basesystem  metapackage-kde4
  [...]
  Installing #305 package of total 420 (200.6M left to get)
  Retrieving ftp://[...]/libgphoto2-2.4.7-2.x86_64.rpm...
  .............................. 100.0% [1.2M (445.4K/s)]                      
  Installing libgphoto2-2.4.7-2.x86_64.rpm...
  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(/usr/lib64/libgphoto2/2.4.7/pccam600.la) into Providename
  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(/usr/lib64/libgphoto2/2.4.7/polaroid_pdc320.la)" records from Providename index
  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(/usr/lib64/libgphoto2/2.4.7/polaroid_pdc640.la)" records from Providename index
  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(/usr/lib64/libgphoto2/2.4.7/polaroid_pdc700.la)" records from Providename index
  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(/usr/lib64/libgphoto2/2.4.7/ptp2.la)" records from Providename index
  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(/usr/lib64/libgphoto2/2.4.7/ricoh.la)" records from Providename index
  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(/usr/lib64/libgphoto2/2.4.7/ricoh_g3.la)" records from Providename index
  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(/usr/lib64/libgphoto2/2.4.7/samsung.la)" records from Providename index
  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 "7c1a292cd9fd0c763e94848f71f6b26cc36990cd" records from Sha1header index
  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.th.pld-linux.org/dists/th/PLD/x86_64/RPMS/libgphoto2-2.4.7-2.x86_64.rpm: installation failed (retcode=-1)
  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/testrpm/var/lib/rpm/Packages
  rpmdb: Open file handle: /root/tmp/testrpm/var/lib/rpm/Name
  rpmdb: Open file handle: /var/lib/rpm/Basenames
  rpmdb: Open file handle: /root/tmp/testrpm/var/lib/rpm/Pubkeys
  rpmdb: Open file handle: /root/tmp/testrpm/var/lib/rpm/Sha1header
  rpmdb: Open file handle: /var/lib/rpm/Triggername
  rpmdb: Open file handle: /var/lib/rpm/Group
  rpmdb: Open file handle: /var/lib/rpm/Requirename
  rpmdb: Open file handle: /var/lib/rpm/Providename
  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.th.pld-linux.org//[...]/gtk+-1.2.10-21.x86_64.rpm...
  .............................. 100.0% [519.8K (519.8K/s)]                 
  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-0.30-0.20080820.23.35.x86_64
  rpm-4.5-33.x86_64

  Tested on count of machines (including virtual machines), this is not
  filesystem or hardware problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/rpm/+bug/574002/+subscriptions