Path: utzoo!utgpu!water!watmath!clyde!att!ihnp4!ucbvax!LBL.GOV!carl%CitHex.Caltech.EDU%KL.SRI.COM%lbl%sfsu1.hepnet
From: carl%CitHex.Caltech.EDU%KL.SRI.COM%lbl%sfsu1.hepnet@LBL.GOV
Newsgroups: comp.os.vms
Subject: Re: Dealing with ACP Errors.
Message-ID: <880528174507.23e03314@LBL.Gov>
Date: 29 May 88 00:45:07 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 43

Received: from KL.SRI.COM by LBL.Gov with INTERNET ;
          Sat, 28 May 88 17:03:12 PDT
Received: from CitHex.Caltech.Edu by KL.SRI.COM with TCP; Tue 24 May 88 05:17:26-PDT
Date:     Tue, 24 May 88 05:21:17 PDT
From:     carl@CitHex.Caltech.Edu (Carl J Lydick)
Message-Id: <880524051242.12e@CitHex.Caltech.Edu>
Subject:  Re: Dealing with ACP Errors.
In-Reply-To: Your message dated 18-Apr-1988
To:       SNAVELY%OUACCVMA.BITNET@CitHex.Caltech.Edu,
         info-vax@CitHex.Caltech.Edu
 
 > The following messages are appearing when a user enters
 > a simple DIR command.
 > 
 > %DIRECT-E-OPENIN, error opening QSA0:(IGR.INC.PRO)*.*;* as input
 > -RMS-E-FND, ACP file or directory lookup failed
 > -SYSTEM-W-BADIRECTORY, bad directory file format
 > 
 > These messages appear after many files in the directory have been listed.
 > 
 > A simple question:
 >  What's the easiest way to deal with this problem?
 >  Am I going to have to re-format the disk and re-load our backup tapes?
 >  If so, how much of a hassle is this?
 
First, RTFM (in this case, Read The F***ing Message).  The problem is NOT
a bad disk, but a directory file that's been corrupted.  So NO you DON'T
have to reformat the disk and re-load your backup tapes (if the directory
was already corrupted when you made the backup, that's a good way to lose
the lost files forever).  Now, the way you deal with this is:
	1)  Use the command:
		$ SET FILE/NODIRECTORY filename
	    where filename is the name of the corrupted directory file.
	    You need to do this because the VERIFY (see step 3) utility will
	    quit when it finds a corrupted directory file.
	2)  Delete the directory file.
	3)  Use the command:
		$ ANALYZE/DISK_STRUCTURE/REPAIR/CONFIRM disk
	    where disk is the disk on which the corrupted directory resides.
	4)  Create a new directory and rename the files from [SYSLOST] to
	    where they belong.
For more details, use the command:
	$ HELP SET FILE/NODIRECTORY