lenny@icus.islp.ny.us (Lenny Tropiano) (06/07/89)
Just recently I dumped a bunch of news ... It was over 20,000 compressed
blocks of news, and my spool partition (/netnews) was sure to run out
of space unbatching it... I just let it unbatch, figuring I applied those
patches 15,16,17 (I think those were the numbers) and all the following
patches to fix up those three.
In the lastest patches there was something added for the threshold to
stop unbatching because of running out of space. I set my threshold to
2,000 blocks. Well when it got to 2,000 blocks I got repeated messages
in my /usr/lib/news/[err]log files that were:
Jun 2 19:10 Unknown inews: Out of space in /netnews. Saving for later processing.
Jun 2 19:10 Unknown inews: Out of space in /netnews. Saving for later processing.
Jun 2 19:10 Unknown inews: Out of space in /netnews. Saving for later processing.
Jun 2 19:10 Unknown inews: Out of space in /netnews. Saving for later processing.
Jun 2 19:10 Unknown inews: Out of space in /netnews. Saving for later processing.
....
I didn't think too much of this, assuming it said "Saving for later processing"
After it was done chugging along, I looked in /netnews/.rnews for those batches
and I found 17 batches that were all "truncated" 0 bytes long. They all
corresponded with the date and time-stamps on the errlog entries. This
has disturbed me, what can I do to prevent this in the future? Were there
patches I missed?
-Lenny
--
Lenny Tropiano ICUS Software Systems [w] +1 (516) 589-7930
lenny@icus.islp.ny.us Telex; 154232428 ICUS [h] +1 (516) 968-8576
{ames,talcott,decuac,hombre,pacbell,sbcs}!icus!lenny attmail!icus!lenny
ICUS Software Systems -- PO Box 1; Islip Terrace, NY 11752