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

Re: git-reflog 70 minutes at 100% cpu and counting

From
EPEric Paris <eparis@redhat.com>
Date
Dec 16, 2009, 13:41 UTC
Message-ID
<1260970885.2788.87.camel@localhost>
In-Reply-To
<alpine.LFD.2.00.0912152201300.23173@xanadu.home>
On Tue, 2009-12-15 at 22:03 -0500, Nicolas Pitre wrote:
Show 6 quoted lines
> On Mon, 14 Dec 2009, Eric Paris wrote:
> 
> > The alternative repo is slowing pushing up to that same location.  That
> > tar is 855838982, so just a tad bit smaller.
> 
> It doesn't appear to be complete yet, and not progressing either.
The alternative repo is now available (but the original is down)

I tried to run git gc --aggressive last night while I slept and got this as output, maybe it helps point to a solution/problem? The git reflog portion ran for 5 hours and 36 minutes and appears to have finished.

$ git gc --aggressive error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 error: Could not read d936ff8a7b0841b51ddf96afa24a30b016824cb2 warning: reflog of 'refs/remotes/audit/master' references pruned commits warning: reflog of 'refs/remotes/btrfs/enospc' references pruned commits warning: reflog of 'refs/remotes/btrfs/merge' references pruned commits warning: reflog of 'refs/remotes/btrfs/for-linus' references pruned commits warning: reflog of 'refs/remotes/security-testing/for-linus' references pruned commits error: Could not read 29b6c2fb1390b4fd350a5ecc78f1156fc5d91e9f fatal: bad tree object 29b6c2fb1390b4fd350a5ecc78f1156fc5d91e9f error: failed to run repack

Previous: Eric ParisNext: Nicolas Pitre
Message 20 of 30 in “git-reflog 70 minutes at 100% cpu and counting”
  1. Eric ParisDec 14, 2009
  2. Sverre RabbelierDec 14, 2009
  3. Jeff KingDec 14, 2009
  4. Eric ParisDec 14, 2009
  5. Jeff KingDec 14, 2009
  6. Eric ParisDec 14, 2009
  7. Sverre RabbelierDec 14, 2009
  8. Nicolas PitreDec 15, 2009
  9. Jeff KingDec 14, 2009
  10. Nicolas PitreDec 15, 2009
  11. Junio C HamanoDec 15, 2009
  12. Nicolas PitreDec 15, 2009
  13. Eric ParisDec 15, 2009
  14. Nicolas PitreDec 15, 2009
  15. Jeff KingDec 15, 2009
  16. Nicolas PitreDec 15, 2009
  17. Eric ParisDec 15, 2009
  18. Nicolas PitreDec 16, 2009
  19. Eric ParisDec 16, 2009
  20. Eric ParisDec 16, 2009
  21. Nicolas PitreDec 16, 2009
  22. Eric ParisDec 16, 2009
  23. Nicolas PitreDec 17, 2009
  24. Eric ParisDec 17, 2009
  25. Nicolas PitreDec 18, 2009
  26. Steven NoonanDec 18, 2009
  27. Eric ParisDec 18, 2009
  28. Nicolas PitreDec 18, 2009
  29. Steven NoonanDec 18, 2009
  30. Eric ParisDec 18, 2009

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.