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

missing objects -- prevention

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Jan 11, 2013, 11:10 UTC
Message-ID
<CAMK1S_jpofLRO02XTYryOP98g7rnrJXs7Mh2zvi=SoVUAs0dUw@mail.gmail.com>
Hi all,

I find a lot of info on how to recover from and/or repair a repo that has missing (or corrupted) objects.

What I need is info on common reasons (other than disk errors -- we've checked for those) for such errors to occur, any preventive measures we can take, and so on. For example, can *any* type of network error or race condition cause this? (Say, can one push writes an object, then fails an update check, and a later push succeeds and races against a gc that removes the unreachable object?) Or... the repo is pretty large -- about 6-7 GB, so could size cause a race that would not show up on a smaller repo?

Anything else I can watch out for or caution the team about?

The symptom is usually a disk space crunch caused by tmp_pack_* files left around by auto-gc. Presumably the missing objects failed the gc and so it left the files around, and they eventually accumulate enough to cause disk full errors. (If a gc ever succeeded, I suspect these files would go away, but that requires manual intervention).

I would appreciate any thoughts...  Thanks!
-- 
Sitaram
Next: Jeff King
Message 1 of 7 in “missing objects -- prevention”
  1. Sitaram ChamartyJan 11, 2013
  2. Jeff KingJan 11, 2013
  3. Sitaram ChamartyJan 12, 2013
  4. Jeff KingJan 12, 2013
  5. Sitaram ChamartyJan 13, 2013
  6. Sitaram ChamartyJan 13, 2013
  7. Jeff KingJan 13, 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.