Skip Navigation Links | |
Exit Print View | |
![]() |
System Administration Guide: Devices and File Systems Oracle Solaris 10 8/11 Information Library |
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)
9. Using InfiniBand Devices (Overview/Tasks)
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)
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
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
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)
The UFS file system relies on an internal set of tables to keep track of inodes used and available blocks. When these internal tables are not properly synchronized with data on a disk, inconsistencies result and file systems need to be repaired.
File systems can be inconsistent because of abrupt termination of the operating system from the following:
Power failure
Accidental unplugging of the system
Turning off the system without proper shutdown procedure
A software error in the kernel
File system inconsistencies, while serious, are not common. When a system is booted, a check for file system consistency is automatically performed (with the fsck command). Often, this file system check repairs problems it encounters.
The fsck command places files and directories that are allocated but unreferenced in the lost+found directory. An inode number is assigned as the name of unreferenced file and directory. If the lost+found directory does not exist, the fsck command creates it. If there is not enough space in the lost+found directory, the fsck command increases its size.
For a description of inodes, see Inodes.