Bug 51077 - Fresh Roswell install yields corrupt RPM database
Fresh Roswell install yields corrupt RPM database
Product: Red Hat Public Beta
Classification: Retired
Component: rpm (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Depends On:
  Show dependency treegraph
Reported: 2001-08-06 23:51 EDT by Christopher Barton
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-07 16:09:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Christopher Barton 2001-08-06 23:51:50 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Description of problem:
Upon installing Roswell, the RPM database is corrupt.  rpm -qa hangs 
forever, part way through the list.

This has happened to me & another user I talk with.  
Copying /var/lib/rpm/* from another Roswell system fixes it.  The URI 
above is a tarball of /var/lib/rpm from an affected system.

How reproducible:

Steps to Reproduce:
1. Install Roswell, reboot
2. Do rpm -qa

Actual Results:  RPM eventually hangs forever.

Expected Results:  RPM should list every package installed on the system.

Additional info:
Comment 1 Glen Foster 2001-08-07 16:09:13 EDT
We (Red Hat) should really try to fix this before next release.
Comment 2 Jeff Johnson 2001-08-07 17:50:22 EDT
Copying an entire database shouldn't be necessary.
If the problem is just "rpm -qa" hangs, the fix is
to do
	rm -f /var/lib/rpm/__db*
This is now always done before opening rpmdb in rpm-4.0.3-0.88.

I'm assuming that that's the problem. If the above doesn't
"fix", please reopen this bug and I'll dig deeper.
Comment 3 Matt Burke 2001-08-12 20:35:33 EDT
The same problem happened to me upgrading from 7.1

The above fix lets rpm -qa work however there are certain entries like:
       error: rpmdb: damaged header instance #1571 retrieved, skipping.

rpm --rebuilddb seems to have cured this.

Whilst I have been affected from this, I have read as much as I can about RPM 
(bar the source code) and nowhere have I seen the __db files documented.  Would 
it be a reasonable idea to have it mentioned somewhere, perhaps the man page?

Note You need to log in before you can comment on or make changes to this bug.