Phase 4 Check Reference Counts - Sun Microsystems Sun Workstation 100U System Manager's Manual

Fsck - UNIX File System Checker Fsck Error Conditions
Possible responses to the RECONNECT prompt are:
YES
reconnect directory inode I to the file system in the directory for lost files (usually
lo,t+ founJ). This may invoke the 10"+ found error condition in Phase 3 if there are prob-
lems connecting directory inode I to 1011+ j(Jund. This may also invoke the CONNECTED
error condition in Phase
3.
if the link was successful.
NO ignore this error condition. This will always invoke the UNREF error condition in Phase 4.
SORRY. NO lost+tound DmECTORY
There is no 1061+ found directory in the root directory of the file system; f,ek ignores the
request to link a directory in lolt+ found. This will always invoke the UNREF error condition
in Phase 4. Check access modes of 1011+ found. See f,ek(8) manual entry for further detail.
This error is ratal if the file system is being preen'ed.
SORRY. NO SPACE IN lost+tound DmECTORY
There is no space to add another entry to the lo,t+ found directory in the root directory of the
file system; fack ignores the request to link a directory in 1011+ found. This will always invoke
the UNREF error condition in Phase 4. Clean out unnecessary entries in 1011+ found or make
1061+ found larger. See f,ck(8) manual entry for further detail. This error is fatal if the file sys-
tem is being preen'ed.
Dm 1=11 CONNECTED. PARENT WAS I=IB
This is an advisory message indicating a directory inode 11 was successfully connected to the
1061+ found directory. The parent inode Ie of the directory inode 11 is replaced by the inode
number of the 1031+ found directory.
A. 7 . Phase 4 - Check Reference Counts
This phase concerns itself with the link count information seen in Phase 2 and Phase 3. This
section lists error conditions resulting from unreferenced files, missing or full lo,t+ found direc-
tory, incorrect link counts for files, directories, symbolic links, or special files, unreferenced files,
symbolic links, and directories, bad and duplicate blocks in files, symbolic links, and directories,
and incorrect total free-inode counts. All errors in this phase are correctable if the file system is
being preen 'ed except running out of space in the lost+ found directory.
UNREF FILE 1=1 OWNER = 0 MODE=M SIZE=S MTIME= T (RECONNECT)
Inode I was not connected to a directory entry when the file system was traversed. The owner
0, mode
M,
size
S,
and modify time
T
of inode
I
are printed. When preen'ing the file is cleared
if either its size or its link count is zero, otherwise it is reconnected.
Possible responses to the RECONNECT prompt are:
YES
reconnect inode I to the file system in the directory for lost files (usually 1011+ /ounJ). This
may invoke the 1031+ found error condition in Phase 4 if there are problems connecting
inode I to 1061+ found.
NO ignore this error condition. This will always invoke the CLEAR error condition in Phase 4.
28 July 1983
15