[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: index corruption (1164) still present in 2.0.15 with db 3.1.17 (ITS#1359)

On Fri, Sep 28, 2001 at 08:41:31AM -0700, Kurt D. Zeilenga wrote:
> At 08:25 AM 2001-09-28, leifj@it.su.se wrote:
> >Full_Name: Leif Johansson
> >Version: 2.0.15
> >OS: Linux 2.2
> >URL: ftp://ftp.openldap.org/incoming/
> >Submission from: (NULL) (
> >
> >The problem described in ITS#1164 -- severe index corruption after multiple
> >modify operations -- which was assumed to have been fixed in the 
> >OPENLDAP_REL_ENG_2 branch still occurs (reproducably) in 2.0.15. If this 
> >release was based on the OPENLDAP_REL_ENG_2 the fix did not work!
> Did you rebuild indices after updating?
> Also, I note you are running an early version of Berkeley DB 3.
> This *may* be part of the problem.  It would be interesting to
> see if the problem is reproducible using Berkeley DB 3.3.11
> or Berkeley 2.7.7.  I note that to try either you would need
> to rebuild your database due to file format changes.

Well, I just tried a bulk-update (70 replace ops on a directory
with ~90k entries) this time using gdbm. This is exactly the type
of modify operation my user management software always does except 
that I modified another attribute this time (the same index though). 

The good news is that there was no index curruption with gdbm! I 
will try a db-3.3.11 version of ldbm now and report back.

	MVH leifj