| Skip Navigation Links | |
| Exit Print View | |
|
System Administration Guide: Devices and File Systems Oracle Solaris 10 1/13 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
System Administration Guide: Devices and File Systems Oracle Solaris 10 1/13 Information Library |
1. Managing Removable Media (Overview/Tasks)
2. Writing CDs and DVDs (Tasks)
4. Dynamically Configuring Devices (Tasks)
5. Managing USB Devices (Tasks)
6. Using InfiniBand Devices (Overview/Tasks)
9. Administering Disks (Tasks)
10. SPARC: Setting Up Disks (Tasks)
11. x86: Setting Up Disks (Tasks)
12. Configuring Oracle Solaris iSCSI Targets (Tasks)
13. The format Utility (Reference)
14. Managing File Systems (Overview)
15. Creating and Mounting File Systems (Tasks)
16. Configuring Additional Swap Space (Tasks)
17. Checking UFS File System Consistency (Tasks)
Enhancements to UFS File System Utilities (fsck, mkfs, and newfs)
Automatic Search for Backup Superblocks
fsck Reports When it Needs to be Rerun
New fsck Messages Regarding Extended Attributes
Better Handling of Duplicate Blocks or Fragments
What the fsck Command Checks and Tries to Repair
Why UFS File System Inconsistencies Might Occur
UFS Components That Are Checked for Consistency
File System Size and Inode List Size Checks
Incorrect "." and ".." Entry Checks
Interactively Checking and Repairing a UFS File System
How to Check the UFS root (/), /usr, or /var File Systems From an Alternate Boot Device
How to Check Other UFS File Systems (Not root (/), /usr, or /var)
How to Preen a UFS File System
Fixing a UFS File System That the fsck Command Cannot Repair
Restoring a Bad UFS Superblock
How to Restore a Bad UFS Superblock (Solaris 10 6/06 Release)
How to Restore a Bad Superblock (Solaris 8, 9, and 10 Releases)
Syntax and Options for the fsck Command
18. UFS File System (Reference)
19. Backing Up and Restoring UFS File Systems (Overview/Tasks)
20. Using UFS Snapshots (Tasks)
21. Copying Files and File Systems (Tasks)
22. Managing Tape Drives (Tasks)
The fsck command uses a state flag, which is stored in the superblock, to record the condition of the file system. This flag is used by the fsck command to determine whether a file system needs to be checked for consistency. The flag is used by the /sbin/rcS script during booting and by the fsck -m command. If you ignore the result from the fsck -m command, all file systems can be checked regardless of the setting of the state flag.
For a description of the superblock, see Superblock.
The possible state flag values are described in the following table.
Table 17-1 Values of UFS File System State Flags
|
|