bug in expire? corrupt history?

[Paul Theodoropoulos]

this is a followup to my messsage of jan 12, regarding inn throttling on

Jan 11 17:25:05 nnrp innd: SERVER cant dbzstore 
[5896A8AD039F14210F44D65600BD43D
8]@0: Invalid argument

along with a gigantic history.pag, relative to history:

-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

in order to get the server going again, i had to wipe out the history, and 
do a complete rebuild from scratch (which takes about ten hours). when it 
was done, i had an approx 1.4G history, and a much more reasonable 150meg 
history.pag.

two days, and two expires have passed, and this morning, my server 
throttled again with

Jan 14 08:25:01 nnrp innd: SERVER cant dbzstore 
[5896A8AD039F14210F44D65600BD43D
8]@0: Invalid argument

same token as before. and, wonder of wonders:

-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

another giant history.pag.

so - is this a bug in expire? a corrupted spool? something else? I'm not 
sure where to go from here.
-----------------------------------------------------------------
Paul Theodoropoulos                    Advanced TelCom Group Inc.
Senior Unix Systems Administrator      Internet Services Division
paul at atgi.net                          Santa Rosa, California, US
Work: http://www.atgi.net         Play: http://www.anastrophe.com