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

ok for git to delete temporary packs on write error?

From
DTDavid Tweed <david.tweed@gmail.com>
Date
Nov 28, 2007, 07:42 UTC
Message-ID
<e1dab3980711272342x7afad721m113fe21f6879a886@mail.gmail.com>

Hi, I'd like to check if there's any reason in the overall design of git which would make deleting tmp_pack's that have suffered write errors a bad idea? (Before I look further into this I may be missing a good reason why they shouldn't be auto-deleted.)

My encounter with this comes from using an almost full usbstick which I discovered when I was poking around for other reasons several partial packs from occasions (separated by weeks) where gc failed. On each failure I'd removed stuff from the drive to clear space and done a successful gc but hadn't thought to check below .git for removable stuff so they'd just accumulated.

Below is a output of a test session:

$ git version git version 1.5.3.6

$ git gc --aggressive --prune
Generating pack...
Done counting 22216 objects.
Deltifying 22216 objects...
 100% (22216/22216) done
Writing 22216 objects...
fatal: sha1 file '/media/usbdiskc/v.git/objects/tmp_pack_QCYYAi' write
error (No space left on device)
error: failed to run repack

$ ls -l /media/usbdiskc/v.git/objects/ total 3944 drwxr-xr-x 2 sis05dst sis05dst 2048 2007-11-28 07:25 info drwxr-xr-x 2 sis05dst sis05dst 2048 2007-11-28 07:25 pack -rwxr-xr-x 1 sis05dst sis05dst 4034560 2007-11-28 07:25 tmp_pack_QCYYAi -rw------- 1 sis05dst sis05dst 0 2007-04-18 23:02 tmp_pack_RYLguI

-- 
cheers, dave tweed__________________________
david.tweed@gmail.com
Rm 124, School of Systems Engineering, University of Reading.
"we had no idea that when we added templates we were adding a Turing-
complete compile-time language." -- C++ standardisation committee
Next: Nicolas Pitre
Message 1 of 3 in “ok for git to delete temporary packs on write error?”
  1. David TweedNov 28, 2007
  2. Nicolas PitreNov 28, 2007
  3. David TweedNov 28, 2007

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.