Tim asks:

> I need to run my disk defrag utility, so I followed the instructions to
> check the
> status of the file system with FSCHECK.  According to the output from
> FSCHECK (see below), there are two files "with no directory entry".
> They are AUTOINST.INSTALL.SYS and AICAT000.INSTALL.SYS.  Also it found a

The firs problem, AUTOINST.INSTALL.SYS and AICAT000.INSTALL.SYS, is
fairly common.  It usually happens as a result of two steps:

first, someone restores @.INSTALL.SYS onto a system ... and those files
(and, often, other files in the INSTALL group and (IIRC) the DIAG group)
get put on ldevs other than 1.  At this point, the system is still
fully functional.

second, an UPDATE is done from an SLT.  The UPDATE brings in the same
files, but puts them on ldev 1 *while the system is "down"*, and it has
no access to the other disk drives, and hence does not delete the
entries for those files from the appropriate label tabels (which are
on ldevs other than 1).  At this point, the system is still fully
functional, but there's a lost file (entry in a label table, disk
still allocated, but no entry in the directory).

FSCHECK notices these lost files and reports them.  The check commands
suggested by the HPRC will fix these problems.  Note: I usually
do a "ask" instead of a "fix", because I don't always trust FSCHECK ...
however, that requires a lot of manual intervention/investigation.
The ordinary user should probably specify "fix".

> "$GROUP/FILESET : PUB.SYS  **UFID NOT IN LABEL TBL".

I'm not sure what causes the above...but I've seen it on a few
systems (which had never run any defrag tool, BTW).  My recollection
is that FSCHECK was able to fix it successfully.   It's probably not
related to the two-step scenario I outlined above ... because the problem
is something *not* in the label table but *in* a directory.

I'd do a full backup and create an SLT before trying to "fix" the
second problem ... just in case.

> copy autoinst.install.sys,autoi.install.sys
> purge autoinst.install.sys
> rename autoi.install.sys

I've done something similar  (I'm not sure of the point of the
exact three statements above):

   :rename autoinst.install.sys, saveauto.install.sys
   :rename aicat000.install.sys, savecat.install.sys

   :fscheck.mpexl.telesup
   checklabel all; ask


PASS 3. Scan Label Table Cache for missing files.
FOUND FILE:AICAT000.INSTALL.SYS   AT 000000CC.0023AC20   WITH NO DIRECTORY ENTRY.
CREATOR :MANAGER SYS
*Verify: 1) Insert into directory, 2) Deallocate file label, 3) Ignore ? 1

FOUND FILE:AUTOINST.INSTALL.SYS   AT 000000CC.0043EF20   WITH NO DIRECTORY ENTRY.
CREATOR :MANAGER SYS
*Verify: 1) Insert into directory, 2) Deallocate file label, 3) Ignore ? 1

   checkdirc  all; ask
   checkextents all
   exit

   :purge autoinst.install.sys   <--- file "created" by FSCHECK
   :purge aicat000.install.sys   <--- file "created" by FSCHECK

   :rename saveauto.install.sys, autoinst.install.sys
   :rename savecat.install.sys, aicat000.install.sys

Why the renames?  Because when I specified option 1 (Insert into directory),
I've now got a file called (in the first case) AICAT000.INSTALL.SYS ... but
that corresponds to an older version of the file!   ...and I'd prefer to
have the newer version.

Of course, if I'd specified option 2 ("deallocate"), I wouldn't have to do
the rename/purge/rename.  I got into the habit of doing option 1 because
prior to 5.0 (IIRC), the "deallocate" had sporadic problems.

--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html