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.

Practice

1. What is the primary purpose of the git fsck command?

easy

A. To check the integrity and validity of objects in a Git repository

B. To clone a remote Git repository

C. To merge two branches automatically

D. To delete untracked files from the working directory

Solution

1. Step 1: Understand the function of git fsck

   The git fsck command scans the Git repository to verify the integrity of objects like commits, trees, and blobs.

2. Step 2: Compare with other Git commands

   Commands like clone, merge, and clean serve different purposes unrelated to repository integrity checks.

3. Final Answer:

   To check the integrity and validity of objects in a Git repository -> Option A

4. Quick Check:

   Repository integrity check = D [OK]

Hint: Remember: fsck means 'file system check' for Git data [OK]

Common Mistakes:

• Confusing git fsck with git clone
• Thinking it modifies files instead of checking
• Assuming it deletes files or merges branches

2. Which of the following is the correct syntax to run a basic integrity check on your Git repository?

easy

A. git fsck --check

B. git check fsck

C. git fsck

D. git fsck --repair

Solution

1. Step 1: Identify the correct command syntax

   The basic command to check repository integrity is simply git fsck without extra flags.

2. Step 2: Understand invalid options

   Options like --check or --repair do not exist for git fsck, and git check fsck is not a valid Git command.

3. Final Answer:

   git fsck -> Option C

4. Quick Check:

   Basic integrity check command = B [OK]

Hint: Use just 'git fsck' to check integrity, no extra flags needed [OK]

Common Mistakes:

• Adding non-existent flags like --check or --repair
• Reversing command order like 'git check fsck'
• Confusing with other Git commands

3. You run git fsck on your repository and see the output:

dangling commit 3a1b2c4d5e6f7g8h9i0j

What does this output mean?

medium

A. The commit is currently checked out in your working directory

B. The repository has corrupted files that must be deleted

C. The repository is fully healthy with no issues

D. There is a commit object not reachable from any branch or tag

Solution

1. Step 1: Understand 'dangling commit' meaning

   A dangling commit is a commit object that exists in the repository but is not referenced by any branch, tag, or other refs.

2. Step 2: Interpret the output context

   This does not mean corruption or errors; it means the commit is orphaned but still present.

3. Final Answer:

   There is a commit object not reachable from any branch or tag -> Option D

4. Quick Check:

   Dangling commit = orphaned but intact commit = A [OK]

Hint: Dangling means unreferenced, not broken [OK]

Common Mistakes:

• Assuming dangling means corrupted
• Thinking the commit is currently active
• Ignoring the meaning of unreachable objects

4. You ran git fsck and got this error:

error: object file .git/objects/ab/cdef1234... is corrupt

What should you do to fix this problem?

medium

A. Restore the corrupted object from a backup or fetch from remote

B. Run git fsck --full to repair the corruption automatically

C. Delete the entire repository and clone it again

D. Ignore the error; it will not affect your repository

Solution

1. Step 1: Understand the error meaning

   The error indicates a corrupted object file in the Git repository, which can cause problems.

2. Step 2: Choose the correct fix approach

   Since git fsck only checks and does not repair, you should restore the corrupted object from a backup or fetch it from a remote repository.

3. Final Answer:

   Restore the corrupted object from a backup or fetch from remote -> Option A

4. Quick Check:

   Corruption fix = restore or fetch = C [OK]

Hint: Restore corrupted objects from backup or remote, fsck only checks [OK]

Common Mistakes:

• Expecting git fsck to repair corruption automatically
• Ignoring corruption errors
• Deleting repo unnecessarily without backup

5. You want to ensure your Git repository is fully healthy before a big release. Which sequence of commands correctly uses git fsck and related steps to check and fix repository integrity?

hard

A. Run git fsck --repair to fix all errors automatically, then commit changes

B. Run git fsck, then if errors appear, restore corrupted objects from backup or remote, then run git fsck again

C. Run git fsck and delete all dangling commits to clean the repo

D. Run git fsck and ignore any warnings about dangling objects

Solution

1. Step 1: Use git fsck to check repository integrity

   Start by running git fsck to detect any corrupted or missing objects.

2. Step 2: Fix detected errors properly

   If errors appear, restore corrupted objects from backup or fetch from remote repositories. Dangling commits usually do not need deletion.

3. Step 3: Verify fixes by rerunning git fsck

   Run git fsck again to confirm the repository is clean and healthy before release.

4. Final Answer:

   Run git fsck, then if errors appear, restore corrupted objects from backup or remote, then run git fsck again -> Option B

5. Quick Check:

   Check, fix, recheck = A [OK]

Hint: Check first, fix from backup, then recheck with git fsck [OK]

Common Mistakes:

• Expecting automatic repair with non-existent flags
• Deleting dangling commits unnecessarily
• Ignoring warnings that could cause issues later