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

git gc ineffective

From
Michal Suchánek <msuchanek@suse.de>
Date
Nov 9, 2020, 09:20 UTC
Message-ID
<20201109092041.GV29778@kitsune.suse.cz>
Hello,
I am running git 2.29.1

I noticed I am running out of disk space, and one repository taking up about 38G. Did git gc --aggressive, and the used space *raised* to 42G, and git would report it does gc after every commit. Did gc without --aggressive, and the used space almost *doubled* to 75G (about 1G is checkout and some utracked files).

The expected size is about 20G. Is there some way to debug gc to figure out what went wrong?

Thanks
Michal
Next: Andreas Schwab
Message 1 of 8 in “git gc ineffective”
  1. Michal SuchánekNov 9, 2020
  2. Andreas SchwabNov 9, 2020
  3. Michal SuchánekNov 9, 2020
  4. Michal SuchánekNov 9, 2020
  5. Michal SuchánekNov 9, 2020
  6. Andreas SchwabNov 9, 2020
  7. Michal SuchánekJan 7, 2021
  8. Johannes SixtJan 7, 2021

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.