How to Check File Systems Interactively

1. Become superuser or assume an equivalent role.

2. Unmount the local file systems except root (/) and /usr.

   # umountall -l

3. Check the file systems.

   # fsck

   All file systems in the /etc/vfstab file with entries in the fsck pass field greater than 0 are checked. You can also specify the mount point directory or /dev/rdsk/device-name as arguments to the fsck command. Any inconsistency messages are displayed.

   For information about how to respond to the error message prompts while interactively checking one or more UFS file systems, see “Resolving UFS File System Inconsistencies (Tasks)” in System Administration Guide: Advanced Administration.

   ---

   Caution –

   Running the fsck command on a mounted file system might cause a system to crash if the fsck command makes any changes, unless stated otherwise, such as running the fsck command in single-user mode to repair a file system.

   ---

4. If you corrected any errors, type fsck and press Return.

   The fsck command might be unable to fix all errors in one execution. If you see the message FILE SYSTEM STATE NOT SET TO OKAY, run the command again. If that does not work, see Fixing a UFS File System That the fsck Command Cannot Repair.

5. Rename and move any files put in the lost+found directory.

   Individual files put in the lost+found directory by the fsck command are renamed with their inode numbers. If possible, rename the files and move them where they belong. You might be able to use the grep command to match phrases with individual files and the file command to identify file types. When whole directories are put into the lost+found directory, it is easier to figure out where they belong and to move them back.

Example—Checking File Systems Interactively

The following example shows how to check the /dev/rdsk/c0t0d0s6 file system and corrects the incorrect block count.

# fsck /dev/rdsk/c0t0d0s6
checkfilesys: /dev/rdsk/c0t0d0s6
** Phase 1 - Check Block and Sizes
INCORRECT BLOCK COUNT I=2529 (6 should be 2)
CORRECT? y

** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Cylinder Groups
929 files, 8928 used, 2851 free (75 frags, 347 blocks, 0.6%
fragmentation)
/dev/rdsk/c0t0d0s6 FILE SYSTEM STATE SET TO OKAY
 
***** FILE SYSTEM WAS MODIFIED *****