Silicon Graphics IRIS Workstation User Manual page 61

Appendix B:
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 fsck should be
made to re-check this file system. If the block was part of the virtual
memory buffer cache, fsck will terminate with the message "Fatal I/O
error" .
NO terminate the program.
CAN NOT READ: BLK B (CONTINUE)
Fsck'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 fsck should be
made to re-check this file system. If the block was part of the virtual
memory buffer cache, fsck will terminate with the message "Fatal I/O
error" .
NO terminate the program.
CAN NOT WRITE: BLK B (CONTINUE)
Fsck'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 check of the file system. A second run of fsck should be
made to re-check this file system. If the block was part of the virtual
memory buffer cache, fsck will terminate with the message "Fatal I/O
error" .
NO terminate the program.
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
Version 1.0
IRIS WORKSTATION GUIDE 57