Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site kitc.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!spuxll!kitc!ladm
From: ladm@kitc.UUCP (John Burgess)
Newsgroups: net.news.adm
Subject: Re: A clue to zero length articles - 2.10.2
Message-ID: <176@kitc.UUCP>
Date: Tue, 27-Aug-85 09:30:31 EDT
Article-I.D.: kitc.176
Posted: Tue Aug 27 09:30:31 1985
Date-Received: Wed, 28-Aug-85 09:44:38 EDT
References: <829@burl.UUCP>
Reply-To: ladm@kitc.UUCP (John Burgess)
Distribution: net
Organization: /usr/local/null
Lines: 31
Summary: Filesystem out of space.

In article <829@burl.UUCP> rcj@burl.UUCP (Curtis Jackson) writes:
>Someone posted an article saying that they had suffered articles (files in
>their news directory [/usr/spool/news, whatever]) that were zero-length
>files.  I, too, have just experienced that problem for the first time;
 ...
>never ran out of free disk space before, either -- until last night.
 ...

Yup, Curtis, that seems to be the problem all right.
We've been losing lots of junk (and probably even a gem or two)
because we keep EVERYthing in /usr/spool (which is its OWN filesystem!)
Because our feed comes in batched, we can run out of space overnight
even when there's over 2000 free blocks at 5PM!

I'm triply hit with this storage technique:
1) /usr/spool/uucp/<the batched input>
2) /usr/spool/news/<the received articles>
3) /usr/spool/newslib/log, history (lists articles even when 0 length!)
		(of course, this doesn't count for much, except
		when running expire history replicates itself!)

Looks like its time for us to
A) cut down on how long we retain groups
and/or
B) enlarge /usr/spool

-- 
John Burgess - Local Tools Administrator
ATT-IS Labs, So. Plainfield NJ  (HP 1C-221)
{most Action Central sites}!kitc!ladm
(201) 561-7100 x2481  (8-259-2481)