Phase 1 Check Blocks And Sizes - Sun Microsystems Sun Workstation 100U System Manager's Manual

Fsck Error Conditions Fsck - UNIX File System Checker
Possible responses to the CONTINUE prompt are:
YES
attempt to continue to run the file system check. Often, however the problem will persist.
This error condition will not allow a complete check of the file system. A second run of '.ck
should
be
made to re-check this file system. If the block was part of the virtual memory
buffer cache, lIck will terminate with the message "Fatal I/O error".
NO terminate the program.
CAN NOT READ: BLK
B
(CONTINUE)
F Ick's request for reading a specified block number B in the file system failed. This should
never happen. See a guru.
Possible responses to the CONTINUE prompt are:
YES
attempt to continue to run the file system check. Often, however, the problem will persist.
This error condition will not allow a complete check of the file system.
A
second run of
I.ck
should be made to re-check this file system. If the block was part of the virtual memory
buffer cache, lIck will terminate with the message "Fatal I/O error".
NO terminate the program.
CAN NOT WRITE: BLK
B
(CONTINUE)
Flek's request for writing a specified block number B in the file system failed. The disk is
write-protected. See a guru.
Possible responses to the CONTINUE prompt are:
YES
attempt to continue to run the file system check. Often, however, the problem will persist.
This error condition will not allow a complete cheek of the file system. A second run of '.ek
should be made to re-check this file system. If the block was part of the virtual memory
buffer cache, lIck will terminate with the message "Fatal I/O error".
NO terminate the program.
A.3.
Phase
1 -
Check Blocks and Sizes
This phase concerns itself with the inode list. This section lists error conditions resulting from
checking inode types, setting up the zero-link-count table, examining inode block numbers for
bad or duplicate blocks, checking inode size, and checking inode format. All errors in this phase
except INCORRECT BLOCK COUNT are fatal if the file system is being preen 'ed,
eg
C:
bad magic number The magic number of cylinder group
C
is wrong. This usually indi-
cates that the cylinder group maps have been destroyed. When running manually the cylinder
group is marked as needing to be reconstructed.
UNKNOWN FILE TYPE 1==1 (CLEAR) The mode word of the inode I indicates that the
inode is not a special block inode, special character inode, socket inode, regular inode, symbolic
link, or directory inode.
Possible responses to the CLEAR prompt are:
10 28 July 1983