I'll throttle the server if it doesn't cooperate!

[Tuc]

Hi,

	We had a crash of a news server recently, and had problems restoring
the backup.  While running it would give alot of "File or directory not
founds" and it would eventually throttle.  You'd go it, and it'd do it again
in either a few minutes, or few hours.  We got tired of it and installed
2.3.0.

	Now we've gotten :

> Subject: innwatch warning: messages in /u1/local/news/log/news.crit
> 
> -rw-rw-rw-    1 news     news            104 Aug 23 20:04 /u1/local/news/log/news.crit
> -----
> Server throttled No such file or directory writing SMstore file -- throttling
> Allowing remote connections
> Parameters c 14 i 50 (0) l 1000000 o 51 t 300 H 2 T 60 X 0 normal specified
> Not reserved
> Readers separate disabled No such file or directory writing SMstore file -- throttling
> Perl filtering enabled
> -----
> Aug 23 20:04:01 news innd: SERVER throttle No such file or directory writing SMstore file -- throttling
> 
> 

	There were also the "can't symlink", "can't write file" like :

Aug 23 18:45:04 news innd: tradspool: could not make directory /u1/local/news/sp
ool/articles/alt/wastewater No such file or directory
Aug 23 18:45:44 news innd: tradspool: could not make directory /u1/local/news/sp
ool/articles/alt/mad/testers/united/to/rule/the/world No such file or directory
Aug 23 18:46:05 news innd: tradspool: could not make directory /u1/local/news/sp
ool/articles/alt/schools/lhhs No such file or directory
Aug 23 19:01:03 news innd: tradspool: could not symlink /u1/local/news/spool/art
icles/alt/personals/motss/women/3 to /u1/local/news/spool/articles/alt/rainwoman
6/1 No such file or directory
Aug 23 19:43:06 news innd: tradspool: could not symlink /u1/local/news/spool/art
icles/alt/homosexual/jay-denebeim/5 to /u1/local/news/spool/articles/alt/madonna
/sucks/cock/5 No such file or directory
Aug 23 20:04:01 news innd: tradspool: could not make directory /u1/local/news/sp
ool/articles/alt/friend/emoji No such file or directory


	(Many more not included)

	We've FSCK'd the disk until blue in the face.  Help?!

		Thanks, Tuc/TTSG