🚀 go-pugleaf

Help!  I am using an entire 135Meg SCSI drive on a 3B2 to store netnews.
The problem is that when I fsck the file system on a daily basis, it almost
always has file damage.  Can anyone tell me what could be causing this?  The
complete configuration is: 3B2/600 running SVR3.2.1.  The disk is a 135 Meg
SCSI device.  The filesystem is advertised read-only using RFS to several
other machines.

Some notes:
  1) Swapping disk drives (including swapping in a 300Meg drive) does not
     help.
  2) Making the main partition smaller than the total disk does not help.
  3) Could the "missing inodes" problem described earlier be causing
     this?  And if so, does anyone have an easy fix?
  4) The damage almost always concerns duplicate blocks, inodes, and
     missing blocks.  Eventually, fsck will never completly fix the
     disk, but rather will always report XXX blocks missing.  At this
     point we usually reformat the disk and start over?

Any help or points would be greatly appreciated.  I would also like to hear
if anyone else is experiencing this problem (as maybe there is some 
underlying bug).  Thanks in advance.

Jon Allen
UUCP:   {...}!att!acpy01!jallen
Domain: jallen@acpy01.att.com