How to fix fatal: missing tree abc1234 in Git

GitADVANCEDHIGH

The 'fatal: missing tree' error occurs when Git cannot find a tree object referenced by a commit or another tree. This indicates repository corruption requiring recovery from backups or remote sources.

What this error means

The "fatal: missing tree" error in Git indicates that your repository is missing a critical tree object that is referenced by a commit or another tree object. In Git's internal data model, a tree object represents a directory snapshot - it maps file names and subdirectory names to their corresponding blob (file content) and tree (subdirectory) objects. When Git stores your project history, it creates three types of objects: blobs (file contents), trees (directory structures), and commits (snapshots linking to root trees with metadata). Each commit points to a "root tree" representing the entire project directory at that moment. If any tree object in this chain is missing, Git cannot reconstruct the directory structure and reports this fatal error. This error is particularly concerning because tree objects are essential for Git to understand your project's file structure. Unlike a missing blob (which only affects a single file), a missing tree can make an entire directory - or even your whole repository - unreadable. The error message includes a partial SHA-1 hash (like "abc1234") identifying which specific tree object Git cannot find.

How to fix "fatal: missing tree abc1234"

1Verify the corruption with git fsck

First, run a filesystem check to understand the extent of the corruption:

bash

# Run a full filesystem check
git fsck --full

# For more detailed output
git fsck --full --verbose

This will list all missing or corrupted objects. Note down the SHA-1 hashes of missing trees - you'll need these for recovery. Look for lines like:
- missing tree abc1234...
- broken link from tree def5678 to tree abc1234
- broken link from commit 123abcd to tree abc1234

2Make a backup of your current repository

Before attempting any repairs, back up your repository to prevent further data loss:

bash

# Create a backup of the entire repository
cp -r /path/to/your/repo /path/to/your/repo-backup

# Or use tar for a compressed backup
tar -czvf repo-backup.tar.gz /path/to/your/repo

This ensures you can retry recovery if something goes wrong during repair attempts.

3Try fetching missing objects from remote

If you have a remote repository (GitHub, GitLab, etc.), try fetching the missing objects:

bash

# Fetch all objects from the remote
git fetch --all

# Or fetch with full depth if it's a shallow clone
git fetch --unshallow

If the standard fetch doesn't work, try fetching specific missing objects:

bash

# Get the list of missing objects and try to fetch them
git fsck --lost-found 2>&1 | grep "missing tree" | awk '{print $3}' | while read hash; do
  git fetch origin $hash || echo "Could not fetch $hash"
done

4Recover objects from a fresh clone

Clone a fresh copy and copy objects from it:

bash

# Clone a fresh copy to a temporary location
git clone <your-remote-url> /tmp/fresh-clone

# Copy all objects from the fresh clone to your corrupted repo
cp -r /tmp/fresh-clone/.git/objects/* /path/to/corrupted/repo/.git/objects/

Alternatively, unpack objects from the fresh clone's pack files:

bash

# Navigate to your corrupted repository
cd /path/to/corrupted/repo

# Unpack objects from the fresh clone
git unpack-objects < /tmp/fresh-clone/.git/objects/pack/pack-*.pack

After copying, verify the fix:

bash

git fsck --full

5Restore from a backup

If you have a backup of your repository, restore the missing objects:

bash

# Copy objects from backup to corrupted repo
cp -r /path/to/backup/.git/objects/* /path/to/corrupted/repo/.git/objects/

# Merge objects directories (preserving existing)
rsync -av /path/to/backup/.git/objects/ /path/to/corrupted/repo/.git/objects/

After restoration, verify and repack:

bash

# Check repository integrity
git fsck --full

# Clean up and optimize if fsck passes
git gc --prune=now

6Rebuild from working directory (last resort)

If remote recovery fails and you have uncommitted work, you can rebuild from your working directory:

bash

# Save your current working directory
cp -r /path/to/repo /path/to/working-copy-backup

# Remove corrupted .git and reinitialize
cd /path/to/repo
rm -rf .git
git init
git remote add origin <your-remote-url>

# Fetch from remote
git fetch origin

# Reset to remote branch, keeping your local files
git reset --mixed origin/main

# Review changes and commit
git status
git add .
git commit -m "Recovered working directory after repository corruption"

Warning: This preserves your working directory but loses local-only commit history.

7Disable cloud sync for .git directory

If cloud sync services caused the corruption, prevent future issues:

For Dropbox:
Create a .dropboxignore file or move the repository outside the Dropbox folder.

For OneDrive:

powershell

# Windows: Exclude .git from OneDrive sync
attrib +U -P /path/to/repo/.git /S /D

For any cloud sync:

bash

# Move repository outside sync folder
mv ~/Dropbox/project ~/projects/project

# Or create repository outside and symlink (not .git)
ln -s ~/projects/project/src ~/Dropbox/project-src

Best practice: Never store Git repositories inside folders synced by cloud services.

8Verify and clean up after recovery

After successful recovery, verify repository integrity and clean up:

bash

# Final integrity check
git fsck --full --strict

# Run garbage collection to optimize
git gc --prune=now --aggressive

# Verify you can access history
git log --oneline -20

# Test checking out different branches
git branch -a
git checkout main

If git fsck reports no errors and you can browse history normally, your repository is recovered.

How to fix fatal: missing tree abc1234 in Git

What this error means

Typical symptoms

Common causes

How to fix "fatal: missing tree abc1234"

Advanced notes

Related errors

Official resources & further reading