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

Re: Recovering from epic fail (deleted .git/objects/pack)

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Dec 10, 2008, 11:39 UTC
Message-ID
<493FAA5A.8070801@viscovery.net>
In-Reply-To
<1228903606.4445.53.camel@starfruit.local>
R. Tyler Ballance schrieb:
Show 7 quoted lines
> On Tue, 2008-12-09 at 16:19 -0800, Junio C Hamano wrote:
>> See if "fsck --full" complains after that.  If the repository was not
>> repacked during that period, all objects created by the activity by the
>> unfortunate developer would be loose, so ...
> 
> tyler@ccnet:~/source/slide/brian_main> time git fsck --full
> Segmentation fault

Please make a backup (tarball) of the repository that shows this segfault. 'git fsck' is not supposed to segfault, no matter what garbage is thrown at it.

Can you make a backtrace of this failing 'git fsck --full' invocation?
-- Hannes
Previous: R. Tyler BallanceNext: R. Tyler Ballance
Message 4 of 22 in “Recovering from epic fail (deleted .git/objects/pack)”
  1. R. Tyler BallanceDec 10, 2008
  2. Junio C HamanoDec 10, 2008
  3. R. Tyler BallanceDec 10, 2008
  4. Johannes SixtDec 10, 2008
  5. epic fsck SIGSEGV! (was Recovering from epic fail (deleted .git/objects/pack))R. Tyler Ballance, Dec 10, 2008
  6. Linus TorvaldsDec 10, 2008
  7. R. Tyler BallanceDec 11, 2008
  8. Linus TorvaldsDec 11, 2008
  9. R. Tyler BallanceDec 11, 2008
  10. Junio C HamanoDec 11, 2008
  11. Boyd Stephen Smith Jr.Dec 11, 2008
  12. Shawn O. PearceDec 11, 2008
  13. Nicolas PitreDec 11, 2008
  14. Junio C HamanoDec 11, 2008
  15. Nicolas PitreDec 11, 2008
  16. Linus TorvaldsDec 11, 2008
  17. Linus TorvaldsDec 11, 2008
  18. Junio C HamanoDec 11, 2008
  19. Linus TorvaldsDec 11, 2008
  20. Linus TorvaldsDec 11, 2008
  21. Junio C HamanoDec 11, 2008
  22. Boyd Stephen Smith Jr.Dec 11, 2008

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.