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

Re: Running out of inodes on an NFS which stores repos

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Sep 9, 2025, 00:29 UTC
Message-ID
<aL904XGUmXmnyXGl@fruit.crustytoothpaste.net>
In-Reply-To
<DCN87S14V9G8.3BAV5XX1BDHKM@gmail.com>
On 2025-09-08 at 07:05:08, Kousik Sanagavarapu wrote:
Show 12 quoted lines
> Yes, I have now set the following config surrounding gc
> 
> 	[receive]
> 		autogc = true
> 	[gc]
> 		auto = 1
> 		autopacklimit = 1
> 
> Curious to know if this will have any noticable performance impact
> though. As I mentioned in my previous msg, these are small repos but the
> number of repos being created and the operations performed on them are
> large - mostly pushes,

The `transfer.unpackLimit` will not have any impact; it's in use at at least some major forges. Packed objects can use things like bitmaps and other functionality, which forges like for performance.

The gc settings you have will cause everything to repacked after every push, and repacking data can be quite expensive. At work, we repack after about every 40 pushes or so. You may wish to use a different value.

-- 
brian m. carlson (they/them)
Toronto, Ontario, CA
Previous: Kousik SanagavarapuNext: Kousik Sanagavarapu
Message 5 of 6 in “Running out of inodes on an NFS which stores repos”
  1. Kousik SanagavarapuSep 6, 2025
  2. rsbecker@nexbridge.comSep 6, 2025
  3. brian m. carlsonSep 6, 2025
  4. Kousik SanagavarapuSep 8, 2025
  5. brian m. carlsonSep 9, 2025
  6. Kousik SanagavarapuSep 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.