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

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

At 02:46 AM 2001-10-02, Leif Johansson wrote:
>On Mon, Oct 01, 2001 at 12:11:00PM -0700, Kurt D. Zeilenga wrote:
>I may have failed to mention this but I am absolutely certain 
>that I am only performing write operations from one client at
>at time in my setup. I.e there is not concurrent write access
>to the database at all!

Noted.  I'm now thinking you are seeing a different class
of problem than I had originally thought.  There appears to
be three different classes of reports, ones related to
concurrency of updates, ones related to non-transactional
behavior of back-ldbm, or yet to be explained problems.

I thought you were seeing concurrency of update issues which
I thought I had resolved.  Apparently your problems are in
one of the other classes.

>> However, as it there might be other problems with back-ldbm,
>> I ask that those who are having reproducible corruption problems
>> test HEAD built w/ -DLDBM_DEBUG_IDL=1.  (I'll commit this debug
>> code to OPENLDAP_REL_ENG_2 soon.)  This code checks index ID lists
>> for consistency.
>Could you do this sooner rather than later --

It was done yesterday...