How To Use Fsck Command To Check And Repair Linux File Systems (2024 Update)

Maintaining a healthy Linux file system is paramount for smooth system operation. File system corruption, often stemming from hardware malfunctions, power failures, or software glitches, can lead to data loss and instability. This guide offers practical fsck commands and examples for checking and repairing Linux file systems.

The fsck (file system check) utility is your key to identifying and resolving file system problems. It can be used manually or configured for automatic checks during system startup. fsck scans for errors, repairs corrupt structures, and flags bad disk blocks to prevent further damage.

Before we delve into fsck commands, remember to identify and unmount the target file systems. Attempting to run fsck on a mounted system is strongly discouraged and can result in data loss.

Caution: Never run these commands on production systems without comprehensive backups. Incorrect usage can lead to data corruption or loss. Practice these commands in a test environment. All commands require sudo or root privileges.

Table of Contents

• Unmounting File Systems
• fsck Commands for File System Repair
  • 1. Dry Run File System Check
  • 2. Check and Repair All File Systems
  • 3. Force File System Check
  • 4. Forced Check with Verbose Output
  • 5. Automatic File System Repair
  • 6. Check ext2, Mark Bad Blocks
  • 7. Mark Bad Blocks (ext2/ext3/ext4)
  • 8. Automatic Repair (ext2/ext3/ext4)
  • 9. Dry Run (ext2/ext3/ext4)
  • 10. Automatic "Yes" to Prompts (ext2/ext3/ext4)
  • 11. Check and Add Bad Blocks to List
  • 12. Forced Check (ext2/ext3/ext4)
  • 13. Verbose Output (ext2/ext3/ext4)
  • 14. Specify Alternative Superblock
  • 15. Force Block Size for Superblock Search
  • 16. Set External Journal Location
  • 17. Add Bad Blocks from File
  • 18. Set Bad Block List from File
  • 19. Find and Report Bad Blocks
  • 20. Forced Check with Bad Block List
• fsck vs. e2fsck
• fsck Command Cheat Sheet
• e2fsck Command Cheat Sheet
• Conclusion

Unmounting File Systems

Always unmount file systems before running fsck. Use df -h or lsblk to identify mounted partitions. Unmount using:

umount /dev/sdXN

(Replace /dev/sdXN with the correct device identifier.) Remount after repair with:

mount /dev/sdXN

fsck Commands for File System Repair

This section details 20 essential fsck commands. Use caution; data loss is possible with incorrect usage. Always back up your data first.

1. Dry Run File System Check

fsck -N

Performs a dry run; shows intended actions without modifying the file system.

2. Check and Repair All File Systems

fsck -As

Checks and repairs all file systems listed in /etc/fstab, skipping those marked "clean."

3. Force File System Check

fsck -f /dev/sda1

Forces a check on /dev/sda1, regardless of its "clean" status.

4. Forced Check with Verbose Output

fsck -fv /dev/sda1

Forces a check with detailed output.

5. Automatic File System Repair

fsck -y /dev/sda1

Automatically repairs /dev/sda1, answering "yes" to all prompts.

6. Check ext2 File System and Mark Bad Blocks

fsck.ext3 -c /dev/sda1

Checks an ext3 file system and uses badblocks to identify and mark bad blocks.

7. Mark Bad Blocks (ext2/ext3/ext4)

e2fsck -c /dev/sda1

Marks bad blocks for ext2/ext3/ext4 file systems.

8. Automatic Repair (ext2/ext3/ext4)

e2fsck -p

Automatically repairs ext2/ext3/ext4 file systems without prompting.

9. Dry Run (ext2/ext3/ext4)

e2fsck -n

Dry run for ext2/ext3/ext4 file systems.

10. Automatic "Yes" to Prompts (ext2/ext3/ext4)

e2fsck -y

Automatically answers "yes" for ext2/ext3/ext4 repairs.

11. Check and Add Bad Blocks to List

e2fsck -c

Checks for and adds bad blocks to the bad block list.

12. Forced Check (ext2/ext3/ext4)

e2fsck -f

Forces a check for ext2/ext3/ext4 file systems.

13. Verbose Output (ext2/ext3/ext4)

e2fsck -v

Provides verbose output for ext2/ext3/ext4 checks.

14. Specify Alternative Superblock

e2fsck -b $Superblock

Specifies an alternative superblock location.

15. Force Block Size for Superblock Search

e2fsck -B $BlockSize

Forces a specific block size during superblock search.

16. Set External Journal Location

e2fsck -j $Dir

Specifies the location of an external journal.

17. Add Bad Blocks from File

e2fsck -l $BadBlocksFile

Adds bad blocks from a specified file to the bad block list.

18. Set Bad Block List from File

e2fsck -L $BadBlocksFile

Sets the bad block list from a specified file.

19. Find and Report Bad Blocks

badblocks -o $BadBlocks.rpt /dev/sda3 $TotalBlockCount

Finds and reports bad blocks, saving the results to a file.

20. Forced Check with Bad Block List

e2fsck -f -l $BadBlocks.rpt /dev/sda1

Forces a check using a pre-existing bad block list.

fsck vs. e2fsck

fsck is a generic file system checker, while e2fsck is specifically for ext2/ext3/ext4. fsck typically calls the appropriate specialized tool (like e2fsck) behind the scenes. Use e2fsck directly for more control over ext2/ext3/ext4 file systems.

fsck Command Cheat Sheet

(Table 1: fsck Commands Cheat Sheet) (Table omitted for brevity, but can be easily reconstructed from the detailed explanations above)

e2fsck Command Cheat Sheet

(Table 2: e2fsck Commands Cheat Sheet) (Table omitted for brevity, but can be easily reconstructed from the detailed explanations above)

Conclusion

Regular file system checks are vital for system health and data protection. This guide provides the tools and knowledge to effectively maintain your Linux file systems. Remember to always back up your data before performing any file system repairs.

The above is the detailed content of How To Use Fsck Command To Check And Repair Linux File Systems (2024 Update). For more information, please follow other related articles on the PHP Chinese website!