git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pete Wyckoff <pw@padd.com>
To: git@vger.kernel.org
Subject: open files limit
Date: Fri, 12 Aug 2011 08:15:48 -0700	[thread overview]
Message-ID: <20110812151548.GA14385@padd.com> (raw)

Somebody at $work found this problem:

    $ git ls-files -s | wc
    error: packfile .git/objects/pack/pack-1627e77da82bbb36118762649c8aa88c05664b1e.pack cannot be accessed
    [..lots more similar errors..]

Turns out his shell's open file descriptor limit was 500.  And
there are 1600 pack files in the repo.

Increasing the descriptor limit to 1024 fixed it.  I could
probably get him to repack, which may also fix it.

Does it seem feasible to look for EMFILE errors and close
some packs?  Or at least spit out a more intuitive error?

		-- Pete

             reply	other threads:[~2011-08-12 15:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 15:15 Pete Wyckoff [this message]
2011-08-12 16:09 ` open files limit Shawn Pearce
2011-08-12 17:26   ` Pete Wyckoff
2011-08-13 20:25     ` [RFC PATCH] test showing EMFILE error with too many packs Pete Wyckoff

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=20110812151548.GA14385@padd.com \
    --to=pw@padd.com \
    --cc=git@vger.kernel.org \
    /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).