Re: (ITS#7862) slapd crash on modifications after host hard reset (in mdb)

[hyc@symas.com]

Vadim Prozorov wrote:
> Excuse me, where I can read about mapasync limitations on Linux?
> http://symas.com/mdb/doc/group__mdb__env.html#gab034ed0d8e5938090aef5ee0997f7e94
> contains no such info. Seems to me I've missed some important info about
> configuration.

MAPASYNC uses msync(... MS_ASYNC). Google for this with Linux will give you 
results like so: http://www.spinics.net/lists/linux-mm/msg71244.html
>
> And in addition - is there way to check DB health status without running slapd?

What health status? The mdb_stat command will return info about the DB.
>
>
> 2014-05-28 15:02 GMT+04:00 Howard Chu <hyc@symas.com <mailto:hyc@symas.com>>:
>
>     Vadim Prozorov wrote:
>
>              Did you have dbnosync configured on this backend? Looks like
>         garbage data
>              got written to the freeDB.
>
>
>         No, DB config section is:
>         # define MDB parameters
>         backendmdb
>         databasemdb
>         maxsize20000000000
>         envflagswritemap mapasync
>         # end define
>
>
>     Unfortunately, in Linux mapasync is a no-op. It seems then that your DB is
>     quite corrupted.
>
>
>     --
>        -- Howard Chu
>        CTO, Symas Corp. http://www.symas.com
>        Director, Highland Sun http://highlandsun.com/hyc/
>        Chief Architect, OpenLDAP http://www.openldap.org/__project/
>     <http://www.openldap.org/project/>
>
>
>
>
> --
> С Ñ?важением,
> Ð?адим Ð?Ñ?озоÑ?ов.
>


-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/