RE: More clues on data corruption bug

["Howard Chu" <hyc@highlandsun.com>]

Someone must have reset your DB environment at some point. There's no way
log002 should have a timestamp newer than log003. I suggest you slapcat the
database to LDIF and delete the entire database. Rebuild OpenLDAP with BDB
4.1.25 before going any further.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: owner-openldap-devel@OpenLDAP.org
> [mailto:owner-openldap-devel@OpenLDAP.org]On Behalf Of Ganesan R
> Sent: Friday, January 24, 2003 5:11 AM
> To: openldap-devel@OpenLDAP.org
> Subject: More clues on data corruption bug
>
>
>
> Hi,
>
> # db_dump -V
> Sleepycat Software: Berkeley DB 4.0.14: (November 18, 2001)
>
> # db_dump dn2id.bdb
> VERSION=3
> format=bytevalue
> type=btree
> db_dump: DB->stat: DB_PAGE_NOTFOUND: Requested page not found
>
> # db_dump id2entry.bdb
> VERSION=3
> format=bytevalue
> type=btree
> db_dump: DB_ENV->log_flush: LSN past current end-of-log
> db_dump: DB_ENV->log_flush: LSN past current end-of-log
> db_dump: DB_ENV->log_flush: LSN past current end-of-log
> db_dump: DB_ENV->log_flush: LSN past current end-of-log
> HEADER=END
> db_dump: DB_ENV->log_flush: LSN past current end-of-log
> db_dump: DB_ENV->log_flush: LSN past current end-of-log
> db_dump: DB_ENV->log_flush: LSN past current end-of-log
> db_dump: DB_ENV->log_flush: LSN past current end-of-log
> db_dump: DB_ENV->log_flush: LSN past current end-of-log
> db_dump: DB_ENV->log_flush: LSN past current end-of-log
> db_dump: DB_ENV->log_flush: LSN past current end-of-log
> db_dump: DB_ENV->log_flush: LSN past current end-of-log
> db_dump: DB_ENV->log_flush: LSN past current end-of-log
> db_dump: DBcursor->get: DB_PAGE_NOTFOUND: Requested page not found
> DATA=END
>
> # db_dump cn.bdb
> db_dump: hash: incompatible hash function
> db_dump: DB->open: cn.bdb:cn: Invalid argument
>
>
> I'll appreciate any help in debugging how this can happen. I also find
> these large log files; what do they mean?
>
> -rw-------    1 root     root     10485752 Jan 20 20:27 log.0000000001
> -rw-------    1 root     casuser  10485689 Jan 24 18:18 log.0000000002
> -rw-------    1 root     casuser   3659715 Jan 22 04:44 log.0000000003
>
> Ganesan
>
> --
> Ganesan R
>
>
>