bugs in expire? corrupt history?

[Mark Hittinger]

> -rw-rw-r--   1 news     news     1518704679 Jan 12 08:16 history
> -rw-rw-r--   1 news     news     2082078872 Jan 12 08:16 history.pag
> -rw-rw-r--   1 news     news     1461649725 Jan 14 08:27 history
> -rw-rw-r--   1 news     news     2135831624 Jan 14 08:27 history.pag

                                   2147483647

Those .pag file sizes are so close to a 32bit signed maxint that it looks
like some calculation is overflowing.  What kind of OS is this on and 
what is the native int size?  Are you using tagged or non-tagged history?

Could you have a conflict with innd's md5 routine and some system library
md5 routine?

Start saving the contents of history.dir before expire so you can see
what the dbzagain estimates would be.

With large files turned on in Solaris and a 3.5 gig history file, my
.hash file is around 500meg and my .index is around 700meg.  (So far
so good).

(ugh) 32bit/64bit "stuff" everywhere just like when we moved out of the 16
bit world.  I know that a few years down the road we'll all be moaning about
hardcoded 0LL's everyplace :-)

Later

Mark Hittinger
Mindspring/Netcom/Dallas
msh at freebsd.org
bugs at freebsd.netcom.com