fsck_s5 Phase 2: check pathnames

This phase removes directory entries pointing to bad inodes found in Phases 1 and 1B. It reports error conditions resulting from:

• incorrect root inode mode and status

• directory inode pointers out of range

• directory entries pointing to bad inodes

Types of error messages--fsck_s5 Phase 2

Phase 2 has four types of error messages:

• informational messages

• Messages with a FIX? prompt, which can be responded to as follows:

  
  no

  Terminate the program because fsck is unable to continue.

  
  y

  Change the root inode type to ``directory.'' If the root inode data blocks are not directory blocks, a large number of error messages are generated.

• Messages with a CONTINUE? prompt, which can be responded to as follows:

  
  n (no)

  Terminate the program.

  
  y (yes)

  Ignore the DUPS/BAD IN ROOT INODE error message and continue to run the filesystem check. If the root inode is not correct, a large number of other error messages might be generated.

• Messages with a REMOVE? prompt, which can be responded to as follows:

  
  n (no)

  Ignore the error condition. A no response is appropriate only if the user intends to take other measures to fix the problem.

  
  y (yes)

  Remove duplicate or unallocated blocks.

fsck_s5 Phase 2 error messages

ROOT INODE UNALLOCATED. TERMINATING

The root inode (usually inode number 2) of the filesystem has no allocate mode bits. This error message indicates a serious problem that causes the program to stop. Call your service representative.

ROOT INODE NOT DIRECTORY (FIX?)

The root inode (usually inode number 2) of the filesystem is not the directory inode type. If the -p option is specified, the program terminates.

DUPS/BAD IN ROOT INODE (CONTINUE?)

Phase 1 or 1B found duplicate blocks or bad blocks in the root inode (usually inode number 2) of the filesystem. If the -p option is specified the program terminates.

I OUT OF RANGE I=I NAME=F (REMOVE?)

A directory entry F has an inode number I that is greater than the end of the inode list. If the -p option is specified the inode is removed automatically.

UNALLOCATED I=I OWNER=O MODE=M SIZE=S MTIME=T NAME=F
(REMOVE?)

A directory entry F has an inode I without allocate mode bits. The owner O, mode M, size S, modify time T, and filename F are printed. If the filesystem is not mounted and the -n option was not specified, the entry is removed automatically if the inode it points to is character size 0. The entry is removed if the -p option is specified.

DUP/BAD I=I OWNER=O MODE=M SIZE=S MTIME=T DIR=F
(REMOVE?)

Phase 1 or Phase 1B found duplicate blocks or bad blocks associated with directory entry F, directory inode I. The owner O, mode M, size S, modify time T, and directory name F are printed. If the -p option is specified, the duplicate or bad blocks are removed.

DUP/BAD I=I OWNER=O MODE=M SIZE=S MTIME=T FILE=F
(REMOVE?)

Phase 1 or Phase 1B found duplicate blocks or bad blocks associated with file entry F, inode I. The owner O, mode M, size S, modify time T, and filename F are printed. If the -p option is specified the duplicate or bad blocks are removed.

BAD BLK B IN DIR I=I OWNER=O MODE=M SIZE=S MTIME=T

This message only occurs when the -D option is used. A physically damaged block was found in directory inode I. Error conditions looked for in directory blocks are non-zero padded entries, inconsistent ``.'' and ``..'' entries, and embedded slashes in the name field. This error message means you should, at a later time, either remove the directory inode (if the entire block looks bad) or change (or remove) those directory entries that look bad.