-----Original Message-----
>From: Bernhard Rosenkraenzer <b...@arklinux.org>
>Sent: 
>To: rpm-devel@rpm5.org
>Subject: rpmdb corruption with 5.3.8
>
>Hi,
>We've just run into a seemingly unfixable rpmdb corruption inside our build 
>system (--> lots of installed packages and lots of activity) on x86_32.
>
>rpm -q and friends are still working, but when trying to modify anything in 
>the rpmdb (e.g. installing a new package), this happens:
>
>
>Preparing...                ########################################### [100%]
>rpmdb: not a restored transaction
>rpmdb: PANIC: Invalid argument
>==> rpmdbe_event_notify(0x9833aa8, PANIC(0), 0xbfe2b5d4) app_private (nil)
>rpmdb: PANIC: fatal region error detected; run recovery
>==> rpmdbe_event_notify(0x9833aa8, PANIC(0), 0xbfe2b6cc) app_private (nil)
>   1:xorg                   ########################################### [ 20%]
>rpmdb: PANIC: fatal region error detected; run recovery
>==> rpmdbe_event_notify(0x9833aa8, PANIC(0), 0xbfe2b5bc) app_private (nil)
>rpmdb: PANIC: fatal region error detected; run recovery
>==> rpmdbe_event_notify(0x9833aa8, PANIC(0), 0xbfe2b50c) app_private (nil)
>error: db3copen:db3.c:1248: db->cursor(-30973): DB_RUNRECOVERY: Fatal error, 
>run database recovery
>rpmdb: illegal flag specified to DB->get
>error: db3cget:db3.c:1305: db->get(22): Invalid argument
>error: error(22) getting records from Name index
>rpmdb: PANIC: fatal region error detected; run recovery
>==> rpmdbe_event_notify(0x9833aa8, PANIC(0), 0xbfe2b72c) app_private (nil)
>rpmdb: PANIC: fatal region error detected; run recovery
>==> rpmdbe_event_notify(0x9833aa8, PANIC(0), 0xbfe2b61c) app_private (nil)
>error: db3copen:db3.c:1248: db->cursor(-30973): DB_RUNRECOVERY: Fatal error, 
>run database 
>recove______________________________________________________________________
RPM Package Manager                                    http://rpm5.org
Developer Communication List                        rpm-devel@rpm5.org

Reply via email to