Re: RPM 4.0.4 database verification failure

[Albert Chin <rpm-list thewrittenword com>]

On Tue, May 14, 2002 at 01:00:26PM -0400, Jeff Johnson wrote:
> On Tue, May 14, 2002 at 11:55:22AM -0500, Albert Chin wrote:
> > On Tue, May 14, 2002 at 10:13:08AM -0400, Jeff Johnson wrote:
> > > On Mon, May 13, 2002 at 07:13:17PM -0500, Albert Chin wrote:
> > > > Created a test package with 4.0.4 (built against DB 4.0.14) on Solaris
> > > > 2.6/SPARC and installed/removed it. Installation went ok. Removal
> > > > returned:
> > > >   $ rpm --dbpath [dir] -e -vv [pkg]
> > > >   ...
> > > >   D: opening  db index       /var/tmp/db/Filemd5s  mode=0x402
> > > >   D: removing 8 entries from Filemd5s index.
> > > >   D: closed   db index       /var/tmp/db/Filemd5s
> > > >   rpmdb: Suspiciously high nelem of 4294967291 on page 0
> > > >   error: db4 error(-30979) from db->verify: DB_VERIFY_BAD: Database
> > > >   verification failed
> > > >   D: verified db index       /var/tmp/db/Filemd5s
> > > >   ...
> > > >   D: closed   db index       /var/tmp/db/Basenames
> > > >   rpmdb: Suspiciously high nelem of 4294967289 on page 0
> > > >   error: db4 error(-30979) from db->verify: DB_VERIFY_BAD: Database
> > > >   verification failed
> > > >   D: verified db index       /var/tmp/db/Basenames
> > > >   ..
> > > > 
> > > > Any ideas? Tried the same package on Redhat 7.1 with rpm-4.0.4-7x and
> > > > didn't have this problem.
> > > 
> > > There's a patch in 4.0.4 that fixes this. Problem is persistent in data, so
> > > a --rebuilddb is needed to eliminate entirely.
> > 
> > So there is a patch in rpm-4.0.4.tar.gz to fix the bug in Berkeley DB
> > 4.0.14? What is the name of the patch file in the RPM tarball?
> 
> It's not an rpm patch, it's a Berkeley db patch that wasn't included in
> db-4.0.14. The patch is in rpm CVS and tarballs produced since
> 
> * Wed Feb 13 2002 Jeff Johnson <jbj@redhat.com>
> - reapply Berkeley DB patch #4491.

Ok, cool. This patch fixed it for us.

-- 
albert chin (china@thewrittenword.com)