[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 07:44 AM 2001-10-03, leifj@it.su.se wrote:
>So should I cc to -its or -bugs??

-its. This attaches the message to the ITS and then forwards it
to -bugs for distribution.

>I have more info. I just tried the REL_ENG_2 with the extra debug
>turned on in idl.c. I assumed that was meant to dump core (assert)
>when something turned up inconsistent? It did not.

Yes. It adds consistency checks which, if fail, case an abort
via assert().

>Another thing
>that strikes me is how _extremely_ repeatable this is. If i do a
>dump+load+operations I get exactly the same corrupted entries that
>I get by doing the same set of operations on the database w/o 
>dump+load. Should I be surprised at this?

Well, I guess I'm not surprised at the moment as I haven't
a clue as to exactly where the problem is (or I'd fix it).

>I may try to change my replaces to adds wherever appropriate and
>see if that affects things -- since it is presumably the objectclass
>index that breaks.

I haven't found anything yet in my digging...  still looking.