Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!snorkelwacker.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!shanega
From: shanega@athena.mit.edu (Shane G. Artis)
Newsgroups: comp.sys.next
Subject: OD thrashing on 2.0 software
Message-ID: <1991Feb11.201046.12640@athena.mit.edu>
Date: 11 Feb 91 20:10:46 GMT
Sender: news@athena.mit.edu (News system)
Reply-To: shanega@athena.mit.edu (Shane G. Artis)
Organization: Massachusetts Institute of Technology
Lines: 21


Hi, I read earlier in this group that someone with a Cube, OD, and
version 2.0 of the software noticed that, when an OD was mounted, sometimes
it would begin to perform huge amounts of activity, reading and spinning,
and the OD could no longer be dismounted.  This is NOT due to a problem with
the optical disk drive, and is, in fact, normal behavior (though undesirable).
I had the same problem on my '030 cube and traced it to a daily administration
task which searches (using 'find') for files suffixed '.nfs' and clears them.
It should (I think) search just the boot disk, but unfortunately it also searches 
the mounted optical disk.  If you are a standalone system, I recommend logging
in as root and removing the last line of the /usr/adm/daily file (make a backup
of course).  This is the source of the problem.

This is just a quick and dirty fix, and may cause problems on networked
machines.  Talk to your administrator.  Anyone have a real fix -  i.e., does
'find' have an option that prevents recursive searches of mounted file systems
or some such thing?



Shane