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

Can a git push over ssh trigger a gc/repack? Diagnosing pack explosion

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Nov 21, 2013, 15:21 UTC
Message-ID
<CACPiFC+TqD_DhMaG+posoK4fTOLCoi=3jhJUPjt_72HTm9xjeQ@mail.gmail.com>
Hi git list,

I am trying to diagnose a strange problem in a VM running as a 'git over ssh server', with one repo which periodically grows very quickly.

The complete dataset packs to a single pack+index of ~650MB. Growth is slow, these are ASCII text reports that use a template -- highly compressible. Reports come from a few dozen machines that log in every hour.

However, something is happening that explodes the efficient pack into an ungodly mess.

Do client pushes over git+ssh ever trigger a repack on the server? If so, these repacking processes are racing with each other and taking 650MB to 7GB at which point we hit ENOSPC, sometimes pom killer joins the party, etc.

pack dir looks like this, ordered by timestamp: http://fpaste.org/55730/04636313/

cheers,
m
-- 
 martin.langhoff@gmail.com
 -  ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 ~ http://docs.moodle.org/en/User:Martin_Langhoff
Next: Martin Langhoff
Message 1 of 4 in “Can a git push over ssh trigger a gc/repack? Diagnosing pack explosion”
  1. Martin LanghoffNov 21, 2013
  2. Martin LanghoffNov 21, 2013
  3. Junio C HamanoNov 21, 2013
  4. Martin LanghoffNov 21, 2013

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.