From: <rsbecker@nexbridge•com>
To: "'Kousik Sanagavarapu'" <five231003@gmail•com>, <git@vger•kernel.org>
Subject: RE: Running out of inodes on an NFS which stores repos
Date: Sat, 6 Sep 2025 11:28:22 -0400 [thread overview]
Message-ID: <03d101dc1f42$e5380a70$afa81f50$@nexbridge.com> (raw)
In-Reply-To: <20250906141711.64419-1-five231003@gmail.com>
On September 6, 2025 10:16 AM, Kousik Sanagavarapu wrote:
>Hello everyone,
>At my $(DAYJOB), we have an NFS which stores different git repos.
>Due to how git stores objects, we have started to run out of inodes on the
NFS as
>the number of repos coming into the NFS increased.
>
>These git repos come from another service and there are typically thousands
of
>them each day. It is important to note that we only store the .git dir and
expose a url
>which is configured as the remote by default to read and write into this
repo.
>
>All of these are small repos; usually not many files and not many commits
too - I'd
>say ~5 commits on average.
>
>Historically, when we ran out of inodes, we had implemented a few
strategies
>where we used to repack the objects or archive the older repos and move
them into
>another store and bring them back into this NFS and unarchive the repo.
>
>However, none of these totally mitigated the issue and we still run into
issue as the
>traffic increases. As a last resort, we increased the disk size even
though there was
>ton of free space left - just for increasing the number of inodes.
>
>We can't delete any of these repos, no matter how old, because they are
valuable
>data.
>
>I was wondering if there was some other strategy that we could implement
here as
>this seems like a problem that people might often run into. It would really
help to
>here your thoughts or if you could point me to anywhere else.
I would suggest running
git gc --aggressive
on your repos. This might help compress your pack files. I have seen
customers
with thousands of pack files who have never run a garbage collection.
Another thing you might want to try is to use sparse-checkout to only keep
the
directories you absolutely need if that is an option. Also, check your /tmp
and
lost+found directories.
next prev parent reply other threads:[~2025-09-06 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-06 14:16 Running out of inodes on an NFS which stores repos Kousik Sanagavarapu
2025-09-06 15:28 ` rsbecker [this message]
2025-09-06 15:34 ` brian m. carlson
2025-09-08 7:05 ` Kousik Sanagavarapu
2025-09-09 0:29 ` brian m. carlson
2025-09-09 7:39 ` Kousik Sanagavarapu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='03d101dc1f42$e5380a70$afa81f50$@nexbridge.com' \
--to=rsbecker@nexbridge$(echo .)com \
--cc=five231003@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox