Carl McNamee wrote:

> In the past I have been told that sometimes you need to reboot the box to
> completely clear out an entry that was purged using FSCHECK.  I ran into
> this after cleaning up a lot of "lost" spool files with FSCHECK.  After the
> reboot the directory was clean again.

(oh, it's quiet for 30 seconds...quick make a post :-)

just to give an update.  the file giving the bad ufid is (was?) in an account
on a private volume...and yes, there is a bad drive in that volume.
unbelievably, though, i don't know *when* the drive failed.  predictive didn't
say anything until yesterday.  i'm guessing that maybe the drive was 'failing'
on saturday when the original problem first occurred.  but the good news
is...no real damage was done.  all the data is this account is temporary so i
don't have to worry about trying to recover any data after the drive is
replaced.  sometimes fortune smiles :-)               - d

--
Donna Garverick     Sr. System Programmer
925-210-6631        [log in to unmask]

>>>MY opinions, not Longs Drug Stores'<<<