Numbers and Symbols
***** FILE SYSTEM WAS MODIFIED *****
Cause
This comment from the fsck(1M) command tells you that it changed the file system
it was checking.
Action
If fsck(1M) was checking the root file system, reboot the system immediately to
avoid corrupting the / partition. If fsck(1M) was checking a mounted file system,
unmount that file system and run fsck(1M) again, so that work done by fsck(1M)
is not undone when in-memory file tables are written out to disk.
** Phase 1– Check Blocks and Sizes
Cause
The fsck(1M) command is checking the file system shown in the messages that are
displayed before this one. The first phase checks the inode list, finds bad or duplicate
blocks, and verifies the inode size and format.
Action
If more than a dozen errors occur during this important phase, you might want to
restore the file system from backup tapes. Otherwise, it is fine to proceed with
fsck(1M).
** Phase 1b– Rescan For More DUPS
Cause
The fsck(1M) command detected duplicate blocks while checking a file system, so
fsck(1M) is rescanning the file system to find the inode that originally claimed that
block.
Action
If fsck(1M) executes this optional phase, you will see additional DUP/BAD
messages in phases 2 and 4.
** Phase 2– Check Pathnames
Cause
The fsck(1M) command is checking a file system, and fsck(1M) is now removing
directory entries pointing to bad inodes that were discovered in phases 1 and 1b.
This phase might ask you to remove files, salvage directories, fix inodes, reallocate
blocks, and so on.
Action
If more than a dozen errors occur during this important phase, you might want to
restore the file system from backup tapes. Otherwise it is fine to proceed with
fsck(1M).
See Also
For more information, see the chapter on checking file system integrity in the System
Administration Guide, Volume 1.
** Phase 3– Check Connectivity
Cause
The fsck(1M) command is checking a file system, and fsck(1M) is now verifying
the integrity of directories. You might be asked to adjust, create, expand, reallocate,
or reconnect directories.
Action
You can usually answer "yes" to all these questions without harming the file system.
** Phase 4– Check Reference Counts
Cause
The fsck(1M) command is checking a file system, and fsck(1M) is now checking
link count information obtained in phases 2 and 3. You might be asked to clear or
adjust link counts.
Action
You can usually answer "yes" to all these questions without harming the file system.
** Phase 5– Check Cyl groups
Cause
The fsck(1M) command is checking a file system, and fsck(1M) is now checking
the free-block and used-inode maps. You might be asked to salvage free blocks or
summary information.
Action
You can usually answer "yes" to all these questions without harming the file system.
***** FILE SYSTEM WAS MODIFIED *****
Cause
This comment from the fsck(1M) command tells you that it changed the file system
it was checking.
Action
If fsck(1M) was checking the root file system, reboot the system immediately to
avoid corrupting the / partition. If fsck(1M) was checking a mounted file system,
unmount that file system and run fsck(1M) again, so that work done by fsck(1M)
is not undone when in-memory file tables are written out to disk.
** Phase 1– Check Blocks and Sizes
Cause
The fsck(1M) command is checking the file system shown in the messages that are
displayed before this one. The first phase checks the inode list, finds bad or duplicate
blocks, and verifies the inode size and format.
Action
If more than a dozen errors occur during this important phase, you might want to
restore the file system from backup tapes. Otherwise, it is fine to proceed with
fsck(1M).
** Phase 1b– Rescan For More DUPS
Cause
The fsck(1M) command detected duplicate blocks while checking a file system, so
fsck(1M) is rescanning the file system to find the inode that originally claimed that
block.
Action
If fsck(1M) executes this optional phase, you will see additional DUP/BAD
messages in phases 2 and 4.
** Phase 2– Check Pathnames
Cause
The fsck(1M) command is checking a file system, and fsck(1M) is now removing
directory entries pointing to bad inodes that were discovered in phases 1 and 1b.
This phase might ask you to remove files, salvage directories, fix inodes, reallocate
blocks, and so on.
Action
If more than a dozen errors occur during this important phase, you might want to
restore the file system from backup tapes. Otherwise it is fine to proceed with
fsck(1M).
See Also
For more information, see the chapter on checking file system integrity in the System
Administration Guide, Volume 1.
** Phase 3– Check Connectivity
Cause
The fsck(1M) command is checking a file system, and fsck(1M) is now verifying
the integrity of directories. You might be asked to adjust, create, expand, reallocate,
or reconnect directories.
Action
You can usually answer "yes" to all these questions without harming the file system.
** Phase 4– Check Reference Counts
Cause
The fsck(1M) command is checking a file system, and fsck(1M) is now checking
link count information obtained in phases 2 and 3. You might be asked to clear or
adjust link counts.
Action
You can usually answer "yes" to all these questions without harming the file system.
** Phase 5– Check Cyl groups
Cause
The fsck(1M) command is checking a file system, and fsck(1M) is now checking
the free-block and used-inode maps. You might be asked to salvage free blocks or
summary information.
Action
You can usually answer "yes" to all these questions without harming the file system.
No comments:
Post a Comment