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

Re: Upgrade to 2.3.40 -> failed index

On Tuesday 05 February 2008 05:22:09 Paul B. Henson wrote:

> There's not much to slapadd, I'm not sure what could have been done
> wrong... I did use the -q option (otherwise it takes untractably long), but
> there were no errors or interruptions and the database created worked fine
> for 10 months or so.
> I distinctly recall there were no log files last year, and I repeated the
> same procedure Sunday again with no log files at the end of the slapadd.
> The documentation says DB_LOG_AUTOREMOVE will "automatically remove log
> files that are no longer needed"; if the db is checkpointed at close
> wouldn't that make the log file unneeded?

No, you would still have one log file at most times, except that ...

> I ran 'strace slapadd -q < /tmp/test.ldif > /tmp/slapadd.out 2>&1'
> There was no log file, and 'grep 'log\.' /tmp/slapadd.out' returned
> nothing.
> Running without the -q, the same grep shows
> 	open("/tmp/test/log.0000000001", O_RDWR|O_CREAT, 0600) = 4
> Evidentally the -q option to slapadd bypasses logging?

-q disables transactions, so there are no transaction logs after a slapadd -q.