better buffindexed configuration possible?

[Anne Wilson]

Hi,

Yesterday I added more newsgroups and more article volume to my server. 
  I have one 512MB buffindexed overview buffer.  Perhaps not 
surprisingly, it couldn't handle the extra load: (pardon the wrapped log 
entries)

Jul  7 17:25:44 imogene innd: buffindexed: ovsetcurindexblock could not 
get new block
Jul  7 17:25:44 imogene innd: buffindexed: could not set current index
Jul  7 17:25:44 imogene innd: buffindexed: no space left for buffer, 
adding 'unidata.binaries.nexrad.HKM'
Jul  7 17:25:44 imogene innd: SERVER cant store overview for 
@03014255464631000000000A3B9600005D61@
Jul  7 17:25:44 imogene innd: SERVER cant write history 
<db41da162506b7b17cd35faf4172840c> Success


Yet, inndf -o reports that only 3% of the space is in use.  Also, my 
active file isn't that large - I currently have only 320 groups, 
although each group probably has a large number of articles.

Some questions:

What is inndf -o actually reporting?  Why is the buffer so sparse?  Can 
I configure it in some way as to use the space better?  I hate to make 
it bigger than it already is if only 3% of the space is currently in use.

Would changing overview.fmt help?  Right now it has the default 
configuration, but I don't really need to save all those header fields.

Also, I'm puzzled by the "SERVER cant write history... Success" message 
- which was it Mr. Dickens???  Assuming it was indeed a failure, why 
would the problem in overview lead to a problem writing the history file?

TIA!

Anne
--
***************************************************
Anne Wilson			UCAR Unidata Program		
anne at unidata.ucar.edu		       P.O. Box 3000
               			  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://my.unidata.ucar.edu/
****************************************************