Appendix B:
Possible responses to the CONTINUE prompt are:
YES
ignore the rest of the blocks in this inode and continue checking with
the next inode in the file system. 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.
NO
terminate the program.
B DUP I=I
Inode I contains block number B which is already claimed by another inode.
This error condition may invoke the EXCESSIVE DUP BLKS error condition in
Phase 1 if inode I has too many block numbers claimed by other inodes. This
error condition will always invoke Phase 1b and the BAD/DUP error condition
in Phase 2 and Phase 4. See Section 4.2.3.
EXCESSIVE DUP BLKS I=I (CONTINUE)
There is more than a tolerable number (usually 10) of blocks claimed by other
inodes. See Section 4.2.3.
Possible responses to the CONTINUE prompt are:
YES
ignore the rest of the blocks in this inode and continue checking
with the next inode in the file system. 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.
NO
terminate the program.
DUP TABLE OVERFLOW (CONTINUE)
An internal table in fsck containing duplicate block numbers has no more room.
Recompile fsck with a larger value of DUPTBLSIZE.
Possible responses to the CONTINUE prompt are:
YES
continue with the program. 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 another duplicate block is
found, this error condition will repeat.
NO
terminate the program.
POSSIBLE FILE SIZE ERROR I=I
The inode I size does not match the actual number of blocks used by the
Version 1.0
IRIS WORKSTATION GUIDE
59
Need help?
Do you have a question about the IRIS Workstation and is the answer not in the manual?