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

Re: [External] git keeps recreating packs, exploding backup increments

From
Pierre Ossman <ossman@cendio.se>
Date
May 9, 2025, 10:27 UTC
Message-ID
<0f0a0dc6-2223-4d59-bc9e-5c8ebfbff09e@cendio.se>
In-Reply-To
<b0b1007c-34a6-4e3f-9982-cfe617affe1a@cendio.se>
Following up on this old thread.

I think the entire thing might be a false diagnostic on our part, and git's default behaviour is working just fine for us.

We initially starting looking at this because the backups exploded in size. But git is complex enough that we had a hard time examining things retroactively. Instead, we started monitoring things going forward to find likely causes.

What we did was to keep an eye on how new the files were in .git/objects/pack. And we kept seeing that the large packs were brand spanking new. Hence, the attempts at reconfiguring git, and the thread here.

But it seems we didn't look close enough. Although the timestamps suggest that the packs are constantly being modified, the names and contents actually stay the same.

I've been keeping a closer eye on a couple of active repositories, and we aren't actually seeing any excessive growth in size. But the largest pack files always have a very current modification time.

No idea what caused that initial spike in backup storage. We'll have to revisit that if it happens again.

Regards,
-- 
Pierre Ossman           Software Development
Cendio AB               https://cendio.com
Teknikringen 8          https://twitter.com/ThinLinc
583 30 Linköping        https://facebook.com/ThinLinc
Phone: +46-13-214600

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Previous: Pierre Ossman
Message 6 of 6 in “git keeps recreating packs, exploding backup increments”
  1. Pierre OssmanFeb 19, 2025
  2. Han YoungFeb 20, 2025
  3. Pierre OssmanFeb 20, 2025
  4. Patrick SteinhardtFeb 21, 2025
  5. Pierre OssmanFeb 24, 2025
  6. Pierre OssmanMay 9, 2025

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.