Git error: solution to object-file-is-empty object files

background

In the daily development process, we may have problems with the Git version library due to improper operation. One of the most common problems is the object file is empty error object-file-is-empty, the general prompt is as follows:

error: object file .git/objects/31/65329bb680e30595f242b7c4d8406ca63eeab0 is empty fatal: loose object 3165329bb680e30595f242b7c4d8406ca63eeab0 (stored in .git/objects/31/65329bb680e30595f242b7c4d8406ca63eeab0)  is corruptCopy the code

Optimal solution

1. Run git FSCK –full

luyi@ubuntu:~/projects/example$ git fsck --full error: object file .git/objects/3a/60046cdd45cf3e943d1294b3cb251a63fb9552 is empty error: object file .git/objects/3a/60046cdd45cf3e943d1294b3cb251a63fb9552 is empty fatal: loose object 3a60046cdd45cf3e943d1294b3cb251a63fb9552 (stored in .git/objects/3a/60046cdd45cf3e943d1294b3cb251a63fb9552)  is corruptCopy the code

2. Select the empty file and delete rm Filepath

luyi@ubuntu:~/projects/example$ rm .git/objects/3a/60046cdd45cf3e943d1294b3cb251a63fb9552 rm: Remove the write - protected regular empty file '. Git/objects / 3 a / 60046 cdd45cf3e943d1294b3cb251a63fb9552 '? yCopy the code

3. Run git FSCK again –full will normally check for a new empty file and delete it. -type f-empty-delete-print will delete all empty files in the.git directory

luyi@ubuntu:~/projects/example/.git$ find . -type f -empty -delete -print
./objects/c6/492f7ad72197e2fb247dcb7d9215035acdca7f
./objects/9f/fe81f4bb7367c00539a9a0d366ff2a7558bfed
./objects/7c/b9a39246389a8417006b9365f6136823034110
./objects/de/1092e8c90cb025e99501a4be0035753b259572
./objects/6f/a8c9109f2e0d29095490ca8f4eaf024a6e2dcb
Copy the code

Git FSCK –full: git FSCK –full: git FSCK –full: git FSCK –full: git FSCK What to do?

luyi@ubuntu:~/projects/example/.git$ git fsck --full
Checking object directories: 100% (256/256), done.
Checking objects: 100% (103719/103719), done.
error: HEAD: invalid sha1 pointer c6492f7ad72197e2fb247dcb7d9215035acdca7f
error: refs/heads/ia does not point to a valid object!
dangling blob 2a12b47881cd879987df8e50c9d900847c025bf4
dangling blob 5d4a7c616f0e59dd82608979e85d56f7a6785884
dangling blob cd6facde8c37f8389c12f3742185174a0536197b
dangling blob c2d0c0fba535d89cca9633d1b0ab780c8199dfd9
dangling blob 5117513970702f484278fd87732135a39588a073
dangling blob ac45f1874a0e42a6b9586594179f9825f3a40fd0
dangling blob c3355ad882b378740822e673d304e2cc091f1412
dangling blob 4d64dedf9f3518f25f7b7e3b1ad0dd6b477e0ce3
dangling blob 2487eae5cc4bfc23bc896c4051cb8f5522664e33
dangling blob 2a1907848af8aea53cb84e392225a5b6c4a81a5b
dangling blob 114233d9981a7933eacbff45a2b106ef1b61cfa9
dangling blob 9879ef3dd84a5515719fa7f35f982ac4d6a34e37
dangling blob f5b3bfd49e04c18ad12d590450a306a109b9151c
dangling blob 5fdb9f048aead1c85474fbca29b2ee327c821680
Copy the code

2. Git /logs/refs/heads/ia

luyi@ubuntu:~/projects/example$ tail -n 2 .git/logs/refs/heads/ia 3a0ecb6511eb0815eb49a0939073ee8ac8674f8a 99 cb711e331e1a2f9b0d2b1d27b3cdff8bbe0ba5 Lu Yi < [email protected] > 1477039998 + 0800 commit: nested into the appCopy the code

6. The head is currently pointing at the latest the a record, so we have a look at the parent commit the penultimate article submitted git cb711e331e1a2f9b0d2b1d27b3cdff8bbe0ba5 show 99

luyi@ubuntu:~/projects/example$ git show 99cb711e331e1a2f9b0d2b1d27b3cdff8bbe0ba5commit 99cb711e331e1a2f9b0d2b1d27b3cdff8bbe0ba5 Date: Fri Oct 21 16:53:18 2016 +0800 nested into app diff --git a/pzbm/templates/pzbm/base.html b/pzbm/templates/pzbm/base.html index 70331c5.. 100644 - a/c96d12c PZBM/templates/PZBM/base. The HTML + + + b/PZBM/templates/PZBM/base. The HTML @ @ - 6, 7 + 6, 7 @ @Copy the code

We can see the content, it’s good

7. Then we will reset the head, the article points to the penultimate git update – ref 99 cb711e331e1a2f9b0d2b1d27b3cdff8bbe0ba5 head

luyi@ubuntu:~/projects/example$ git update-ref HEAD 99cb711e331e1a2f9b0d2b1d27b3cdff8bbe0ba5
luyi@ubuntu:~/projects/example$ git s
On branch ia
Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

    modified:   pzbm/templates/pzbm/invest_advisor/reports.html

Copy the code

8. Finally submit the following new code and it is OK. This will keep our Git log, just to fix the bad nodes.

Git command collation

Blog Source: Blog of rainy Night