.th DCC VIII 4/21/86
.sh NAME
dcc - directory consistency check
.sh SYNOPSIS
dcc [-j <jnumbers>] <seid> <extent>
.sh DESCRIPTION
Dcc examines the KSOS file system residing on the specified extent and
reports any inconsistencies.  The <seid> argument has the following
form:
.sp
.lp 13 0
dx/y
.i0
.sp
where d indicates a device, x is the uniq_id0 and y is the uniq_id1 of
the seid of the device on which the desired extent resides.
.s3
Diagnostic messages report the following inconsistencies:
.s3
.lp 13 2
-	Directory entries which point outside the file system (whose
name space is not 'same_nsp').
This can be caused by the system being stopped without mounted filesystems
being unmounted.
Also, there are directory entries which normally point to things other
than files (userPBB and serverPBB, for example).
.s3
.lp 13 2
-	Directory entries which correspond to invalid jnumbers (uniq_id1
field is out of range).
This normally should not occur, and is considered a serious error.
.s3
.lp 13 2
-	Jnodes whose link count does not equal the actual number of directory
entries pointing to them.
This is only serious if the jnode link count is less that the actual number
of links.
.s3
.lp 13 2
-	Non-jnode items which are pointed to by directory entries.
This normally should not occur, and is considered a serious error.
.i0
.s3
If the -j option is specified along with a list of j-numbers,
a diagnostic message will be produced for each directory entry which
points to that jnode.
.s3
Normal diagnostic messages have the following format:
.s3
.lp 13 0
<jdir>: <seid> '<name>' -- <message>
.i0
.s3
where <jdir> is the j-number of the directory,
<seid> and <name> identify the particular directory entry,
and <message> corresponds to one of the conditions listed above.
.sh "SEE ALSO"
STC(VIII)
.sh NOTES
No audit capture messages are sent.
