git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: corrupt object on git-gc

From
YLYossi Leybovich <sleybo@gmail.com>
Date
Nov 9, 2007, 15:01 UTC
Message-ID
<4fe79b4b0711090701g7a43cdfdi5e20e5ffb437d7bb@mail.gmail.com>
In-Reply-To
<473464A2.7080003@op5.se>
On Nov 9, 2007 8:46 AM, Andreas Ericsson <ae@op5.se> wrote:
Show 5 quoted lines
>
> Is this a super-secret project or you can make a tarball of the .git
> directory and send it to me? Trying to track down the cause through
> email is decidedly slow.
>

Actually yes , I am not sure I can send the repository , I will farther check that.

Show 10 quoted lines
>
> One tree uses the object. I'm not sure if any commit-objects
> use the tree. Try
>
> for b in $(git branch --no-color -a | cut -b3-); do
> for rev in $(git rev-list HEAD); do
>        git ls-tree -r $rev | grep -q 2d9263c6d23595e7cb2a21e5ebbb53655278dff8
>        test $? -eq 0 && echo $rev && break
> done
> done
tried this and it return empty

[mellanox@mellanox-compile ib]$ [mellanox@mellanox-compile ib]$ for b in $(git branch --no-color -a | cut -b3-); do

> for rev in $(git rev-list HEAD); do
> git ls-tree -r $rev | grep -q 2d9263c6d23595e7cb2a21e5ebbb53655278dff8;
> test $? -eq 0 && echo $rev && break;
>  done; done

[mellanox@mellanox-compile ib]$ [mellanox@mellanox-compile ib]$

[BTW I didn't notice u use the b varieble so I also tried gi rev-list $b but still empty ] I also tried to remove object and tree and apperently other trees and commits reference to these objects

 mv ../9458b3786228369c63936db65827de3cc06200  ../4b/
mv: cannot stat `../9458b3786228369c63936db65827de3cc06200': No such
file or directory
[mellanox@mellanox-compile ib]$ mv
.git/objects/4b/9458b3786228369c63936db65827de3cc06200  ../4b/
[mellanox@mellanox-compile ib]$ mv
.git/objects/2d/9263c6d23595e7cb2a21e5ebbb53655278dff8  ../2d/
[mellanox@mellanox-compile ib]$ git-fsck --full
broken link from    tree e5a0044c4ccae7635f07414c1f155bac72d25fd9
              to    tree 2d9263c6d23595e7cb2a21e5ebbb53655278dff8
dangling commit 0d43a63623237385e432572bf61171713dcd8e98
dangling commit 4fc6b1127e4a7f4ff5b65a2dd8a90779b5aff3e0
dangling commit 7da607374fe2b1ae09228d2035dd608c73dad7c8
dangling commit 004ef09ae022c60a30f9cd61f90d18df5db3628e
broken link from    tree 8bd00402b2a20024f4556107b8a729b0205657db
              to    tree 2d9263c6d23595e7cb2a21e5ebbb53655278dff8
dangling commit 85112c6fabb6b8913ab244a8645d67380616eba6
missing tree 2d9263c6d23595e7cb2a21e5ebbb53655278dff8
dangling commit bd98481afa93356fa6daa4b6f88c4e631ae2fd72
dangling commit e81e3d2c9c25e5bf5b31327b10b23f9bd0a6d056
dangling commit 92ff9b8cbc771345c9cde0c7fef2c23bb79242b9
Show 6 quoted lines
>
> If it turns up empty, you *should* be able to safely delete
> 2d9263c6d23595e7cb2a21e5ebbb53655278dff8 and
> 4b9458b3786228369c63936db65827de3cc06200
>
> Make sure to take a backup first though.
a lot of commits and trees point to this
Show 6 quoted lines
>
> --
> Andreas Ericsson                   andreas.ericsson@op5.se
> OP5 AB                             www.op5.se
> Tel: +46 8-230225                  Fax: +46 8-230231
>
Previous: Andreas EricssonNext: Johannes Sixt
Message 3 of 20 in “Re: corrupt object on git-gc”
  1. Yossi LeybovichNov 9, 2007
  2. Andreas EricssonNov 9, 2007
  3. Yossi LeybovichNov 9, 2007
  4. Johannes SixtNov 9, 2007
  5. Yossi LeybovichNov 9, 2007
  6. Johannes SixtNov 9, 2007
  7. Nicolas PitreNov 9, 2007
  8. Yossi LeybovichNov 9, 2007
  9. Nicolas PitreNov 9, 2007
  10. Linus TorvaldsNov 9, 2007
  11. add a howto document about corrupted blob recoveryNicolas Pitre, Nov 9, 2007
  12. Johannes SchindelinNov 9, 2007
  13. J. Bruce FieldsNov 26, 2007
  14. Yossi LeybovichNov 9, 2007
  15. Linus TorvaldsNov 9, 2007
  16. Yossi LeybovichNov 9, 2007
  17. Linus TorvaldsNov 9, 2007
  18. Mike HommeyNov 9, 2007
  19. Yossi LeybovichNov 9, 2007
  20. Mike HommeyNov 9, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.