11 Feb
2014
11 Feb
'14
11:42 a.m.
Dump of file SYS$SYSROOT:[000000]SYSMAINT.DIR;1
...
File identification: (773,74,0)
Directory DUA0:[SYS0]
...
SYSMAINT.DIR;1 (773,74,0)
Directory DUA0:[000000]
...
SYSMAINT.DIR;1 (773,74,0)
Looks like the same directory is in both higher level directories.
I assume copy the directory to new, delete and analyze/repair again
and hope it cleans it up.
This is not necessarily a problem. It is allowed for a file (or a directory)
to be entered in more than one directory. Disks set up for clustering in
later versions of VMS make use of this for example.
I haven't come across a SYSMAINT.DIR entered in [000000] but it could be there
for a reason. It may be possible to get rid of it with:
$ SET FILE /REMOVE DUA0:[000000]SYSMAINT.DIR;1
if MicroVMS 4.6 has this command. Any files in DUA0:[SYSMAINT] would remain
visible from DUA0:[SYS0.SYSMAINT]. However I would leave it alone in case
something wants it there. It shouldn't do any harm.
Have a look at the field called "Back link file identification:" when you
dump the file header. This specifies the FID of the directory that the file
is entered into. If the same file is entered in more than one directory, this
information can only be correct for one of the directories.
In even slightly more recent versions of VMS, such as V5.5-2, ANALYZE /DISK
does not complain about this apparant anomaly but I think I recall vaguely
that this was not always the case.
Regards,
Peter Coghlan.