git fsck for repository integrity - Commands & Configuration

Introduction

Sometimes your Git repository can get corrupted or have broken links. The git fsck command checks your repository for problems and helps you find broken or missing objects.

When you suspect your Git repository is corrupted after a failed operation.

When you want to verify that all commits and objects in your repository are intact.

Before pushing or pulling to ensure your local repository is healthy.

After recovering files from backup to check repository consistency.

When troubleshooting strange Git errors related to missing objects.

Commands

This command checks the integrity of your Git repository. It looks for missing or corrupted objects and reports any problems it finds.

Terminal

git fsck

Expected Output

Checking object directories: 100% (256/256), done.

Checking objects: 100% (1234/1234), done.

This runs a more thorough check of the repository, verifying all objects and their connectivity.

Terminal

git fsck --full

Expected Output

Checking object directories: 100% (256/256), done.

Checking objects: 100% (1234/1234), done.

No errors found.

→

--full - Performs a complete check of all objects and connectivity

This command finds dangling or unreachable objects and saves them in .git/lost-found for recovery.

Terminal

git fsck --lost-found

Expected Output

Checking object directories: 100% (256/256), done.

Checking objects: 100% (1234/1234), done.

Dangling commit 9fceb02

Dangling blob 3a1b2c4

Saved dangling objects to .git/lost-found/

→

--lost-found - Recovers dangling objects by saving them for inspection

Key Concept

If you remember nothing else from this pattern, remember: git fsck helps you find and fix broken or missing parts inside your Git repository.

Common Mistakes

Running git fsck without understanding the output

You might see warnings or dangling objects and get confused about what to do next.

Learn to read the output carefully; dangling objects are not always errors but may indicate unreferenced data.

Ignoring errors reported by git fsck

Ignoring errors can lead to bigger problems like failed commits or pushes later.

Investigate and fix reported errors promptly to keep your repository healthy.

Summary

git fsck checks your Git repository for broken or missing objects.

Use git fsck --full for a complete integrity check.

Use git fsck --lost-found to recover dangling objects.