From: Avery Pennarun <apenwarr@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: Funny error with git gc...
Date: Fri, 15 May 2009 14:24:19 -0400 [thread overview]
Message-ID: <32541b130905151124l40194e3eq78411c5b94bd9598@mail.gmail.com> (raw)
In-Reply-To: <7vmy9etey8.fsf@alter.siamese.dyndns.org>
On Fri, May 15, 2009 at 2:10 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> if you need a chuckle, like me, you might appreciate this story: in one of
>> my repositories, "git gc" dies with
>>
>> unable to open object pack directory: ...: Too many open files
>>
>> turns out that there are a whopping 1088 packs in that repository...
>
> Isn't it a more serious problem than a mere chuckle? How would one
> recover from such a situation (other than "mv .git/objects/pack-*;
> for p in pack-*.pack; do git unpack-objects <$p; done")?
I guess if you have root access, you could increase your file ulimit
(-n) temporarily and then repack. Of course that's not actually
addressing the root cause of the problem.
Avery
next prev parent reply other threads:[~2009-05-15 18:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 18:02 Funny error with git gc Johannes Schindelin
2009-05-15 18:10 ` Junio C Hamano
2009-05-15 18:24 ` Avery Pennarun [this message]
2009-05-15 18:46 ` Linus Torvalds
2009-05-15 19:08 ` Johannes Schindelin
2009-05-15 19:12 ` Johannes Schindelin
2009-05-15 19:18 ` Johannes Schindelin
2009-05-15 20:08 ` Linus Torvalds
2009-05-23 8:53 ` Johannes Schindelin
2009-05-23 16:02 ` Linus Torvalds
2009-05-24 17:37 ` Johannes Schindelin
2009-05-15 19:16 ` Linus Torvalds
2009-05-15 19:24 ` Johannes Schindelin
2009-05-15 20:30 ` Daniel Barkalow
2009-05-18 8:28 ` Matthias Andree
2009-05-15 18:52 ` [MAKESHIFT PATCH] Cope better with a _lot_ of packs Johannes Schindelin
2009-05-15 19:17 ` Shawn O. Pearce
2009-05-21 1:22 ` Junio C Hamano
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=32541b130905151124l40194e3eq78411c5b94bd9598@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).