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

[RFC] Avaiable disk space when automatic garbage collection kicks in

From
DSDragan Simic <dsimic@manjaro.org>
Date
Apr 8, 2024, 16:29 UTC
Message-ID
<950d4ad3bcee79df1424faee09eb6b00@manjaro.org>
Hello all,

A few days ago I've noticed a rather unusual issue, but still a realistic one. When automatic garbage collection kicks in, as a result of gc.auto >= 0, which is also the default, the local repository can be left in a rather strange state if there isn't enough free space available on the respective filesystem for writing the objects, etc.

It might be a good idea to estimate the required amount of free filesystem space before starting the garbage collection, be it automatic or manual, and refuse the operation if there isn't enough free space available.

As a note, the need_to_gc() function already does something a bit similar with the available system RAM.

Any thoughts?
Next: Dragan Simic
Message 1 of 4 in “[RFC] Avaiable disk space when automatic garbage collection kicks in”
  1. Dragan SimicApr 8, 2024
  2. Dragan SimicJun 12, 2024
  3. rsbecker@nexbridge.comJun 12, 2024
  4. Dragan SimicJun 12, 2024

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.