tewksbur@bu-cs.BU.EDU (Chip Tewksbury) (05/14/89)
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.
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.
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!:-))
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.
Thanks,
Chip Tewksbury, Distributed Systems Group, Boston University,
111 Cummington Street, Boston, MA 02215, USA (617) 353-2780
INTERNET: tewksbur@bu-it.bu.edu BITNET: TEWKSBUR@BUENGA
UUCP: {}!harvard!bu-cs!bu-it!tewksbur