JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
System Administration Guide: Devices and File Systems     Oracle Solaris 10 8/11 Information Library
search filter icon
search icon

Document Information

About This Book

1.  Managing Removable Media (Overview)

2.  Managing Removable Media (Tasks)

3.  Accessing Removable Media (Tasks)

4.  Writing CDs and DVDs (Tasks)

5.  Managing Devices (Overview/Tasks)

6.  Dynamically Configuring Devices (Tasks)

7.  Using USB Devices (Overview)

8.  Using USB Devices (Tasks)

9.  Using InfiniBand Devices (Overview/Tasks)

10.  Managing Disks (Overview)

11.  Administering Disks (Tasks)

12.  SPARC: Setting Up Disks (Tasks)

13.  x86: Setting Up Disks (Tasks)

14.  Configuring Oracle Solaris iSCSI Targets and Initiators (Tasks)

15.  The format Utility (Reference)

16.  Managing File Systems (Overview)

17.  Creating and Mounting File Systems (Tasks)

18.  Using The CacheFS File System (Tasks)

19.  Configuring Additional Swap Space (Tasks)

20.  Checking UFS File System Consistency (Tasks)

UFS File System Consistency

How the UFS File System State Is Recorded

What the fsck Command Checks and Tries to Repair

Why UFS File System Inconsistencies Might Occur

UFS Components That Are Checked for Consistency

Superblock Checks

File System Size and Inode List Size Checks

Free Block Checks

Free Inode Checks


Format and Type of Inodes

Link Count Checks

Duplicate Block Checks

Bad Block Number Checks

Inode Size Checks

Indirect Blocks

Data Blocks

Directory Unallocated Checks

Bad Inode Number Checks

Incorrect "." and ".." Entry Checks

Disconnected Directories

Regular Data Blocks

fsck Summary Message

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)

Preening UFS File Systems

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

21.  UFS File System (Reference)

22.  Backing Up and Restoring UFS File Systems (Overview)

23.  Backing Up UFS Files and File Systems (Tasks)

24.  Using UFS Snapshots (Tasks)

25.  Restoring UFS Files and File Systems (Tasks)

26.  UFS Backup and Restore Commands (Reference)

27.  Copying Files and File Systems (Tasks)

28.  Managing Tape Drives (Tasks)


How the UFS File System State Is Recorded

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 20-1 Values of UFS File System State Flags

State Flag Value
Indicates a mounted file system that has modified data in memory. A mounted file system with this state flag indicates that user data or metadata would be lost if power to the system is interrupted.
Indicates that the file system contains inconsistent file system data.
Indicates an undamaged, cleanly unmounted file system.
Indicates that the file system has logging enabled. A file system with this flag set is either mounted or unmounted. If a file system has logging enabled, the only flags that it can have are FSLOG or FSBAD. A file system that has logging disable can have FSACTIVE, FSSTABLE, or FSCLEAN.
Indicates an idle mounted file system. A mounted file system with this state flag indicates that neither user data nor metadata would be lost if power to the system is interrupted.