[Info-vax] Problems detected with analyze/disk

[JF Mezei]

anwa wrote:

> %ANALDISK-W-MULTALLOC, file (288980,11,0) TCPIP$REXEC_RUN.LOG;185
>         multiply allocated blocks
>         VBN 1 to 16
>         LBN 36358752 to 36358767, RVN 1
> %ANALDISK-W-MULTALLOC, file (708146,53,0) °ç 0ê Pê
>         multiply allocated blocks
>         VBN 99681 to 99696
>         LBN 36358752 to 36358767, RVN 1


Second one is pretty strange since the file name is not valid.

DUMP /ID=(708146,53,0)  sys$login:login.com will give you the file name
of the file, assuming your current directory is the same as that of the
device that holds that file ( it appears you still have to provide some
valid file name in the DUMP command as part of the CLI definition).


There is a utility called "DIX" which runs in X windows which allows you
to peruse the INDEXF.SYS file. You might be able to modify the records
of the offending files to mark them as deleted.

Say a phantom file has 100 allocated, 10 of which also belong to another
file. After doing it, an ANA/DISK/REPAIR would spot 90 deleted blocks
that can be freed and leave the other 10 belonging to the original file.

Normally, such errors should not happen. But we've all experienced a few
of those. But the ones you have seem odd in that the file names are
totally out of whack. Could be some software that is very low level and
which corrupts your indexf.

If you have that many, you might wish to backup/image and restore it.
Backup would recreate those phantom files in the new disk, but each
would have its own copy of the data, no shared blocks.