From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 17-MAY-1989 19:07
To:	MRGATE::"ARISIA::EVERHART"
Subj:	No Subject

Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Mon, 15 MAY 89 08:11:46 PDT
Received: from scivax.STSCI.EDU by KL.sri.com with TCP; Mon, 15 May 89 07:59:08 PDT
Received: by scivax id <202026D60F1@scivax.STSCI.EDU> ;
       Mon, 15 May 89 10:57:49 EDT
Date: Mon, 15 May 89 10:57:45 EDT
From: "Chairman, Von Neumann Catastrophe Relief Fund" <TCOMEAU@scivax.STSCI.EDU>
To: info-vax@kl.sri.com
X-Vms-Mail-To: EXOS%"info-vax@kl.sri.com"
Message-Id: <890515105745.202026D60F1@scivax.STSCI.EDU>

Chip Tewksbury writes:
>	I just got back from DECUS and one thing that really bothered me 
>was a presentation at the VAX Magic session.  A particular gentleman spoke 
>of his perils with ANALYZE/DISK/REPAIR on his V5.0 system.
>
I was that guy, and my presentation wasn't on ANAL/DISK, but on the perils
of VMSINSTAL on V5.1.

If you fail to do an ANAL/DISK/REPAIR after installing V5.1, you will have
blocks in use marked as available, and in our case a free block included
a block in the RMS.EXE image.  My Magic presentation didn't mention bugs
in ANAL/DISK, only the problem with VMSINSTAL that was repaired with ANAL/DISK.

>
>	The part that was bothersome was that he incorrectly told people to
>verify their disks three times.    He failed to mention that there is a bug
>in VERIFY where you have to "DEFINE SYS$SCRATCH some_other_disk:"   before 
>running ".../REPAIR" or you will (may) build a corrupt BITMAP.SYS file.
>

The reason I recommend doing three passes is that the first time through
you'll see many "blocks allocated marked free"; the second time through
you'll see many "blocks free marked allocated"; the third time you'll see
nothing.  You can probably do it only twice and get a clean disk - we do
it thrice so our less-experienced system managers see only 'clean screens'
when it works.

>	I don't know if anyone else caught his mistake, but I was unsure as
>to how to go about correcting it in that type of environment.  (Probably just
>jump up and shout!:-)) 
>

Actually, go to the mike, state your name and affilliation, then shout.  
Warning:  Don't do this at nightclubs :-}.

>	Anyway,  I'm not sure if it's fixed in V5.1(-x)  but if anyone else
>was there who heard this and can corroborate or deny my story, please do so.

I don't know of any bugs in ANAL/DISK, we haven't found any in V5.1, and the
Digital people I talked to didn't mention any problems with file system 
utilities.  (I didn't ask about ANAL/DISK specifically, but did talk to 
a couple of VMS people about my trials with the V5.1 install.)

I'm sorry if I wasn't clear:  I don't know of any problems with ANAL/DISK in
V5.1, but I do know that if you don't do an ANAL/DISK/REPAIR after installing
V5.1, you will likely have problems.

tc>

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Tom Comeau (Chair, Von Neumann Catastrophe Relief Fund)
Space Telescope Science Institute
tcomeau@scivax.stsci.edu
------------------------------------------------------------------------
The opinions expressed are my own.  Don't blame anyone else.
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv