Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!shanega
From: shanega@athena.mit.edu (Shane G. Artis)
Newsgroups: comp.sys.next
Subject: Re: Lost 6 Megs of Hard Disk space
Message-ID: <1991Jun12.194751.23063@athena.mit.edu>
Date: 12 Jun 91 19:47:51 GMT
References: <676362343.59@egsgate.FidoNet.Org> <202@magus.UUCP>
Sender: news@athena.mit.edu (News system)
Organization: Massachusetts Institute of Technology
Lines: 18

In article <202@magus.UUCP> zack@magus.UUCP (Zacharias_Beckman) writes:
>I hate to tell you this -- but I will, since it may save you great headaches
>in the future.  According to NeXT (reliable lines internally, as we have a
>good relationship with them) you MUST NEVER, EVER, EVER run fsck manually.  I
>did once upon a time.  Had to rebuild the machine eventually.
>
>Now, I'm not sure that this applies to single user mode.  But, even on a
>generic Unix system it's not a good idea to run fsck while booted multi-user.
>I wish you luck in not having to rebuild!

Could you expand and clarify these statements a bit?  Fsck is an important
tool, and I have used it in the past on my NeXT.  What exactly did NeXT
say about its use, and what should we do instead of using it when it becomes
necessary?

Thank-you,

Shane