All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Rabbitson <rabbit@rabbit.us>
To: git@vger.kernel.org
Subject: [BUG] Incorrect/misleading error when `git rev-list --objects --all` hits the max open files limit
Date: Mon, 4 Mar 2013 10:29:27 +1100	[thread overview]
Message-ID: <20130303232927.GA16606@rabbit.us> (raw)

Hi!

I was tinkering with a massive git repository (actually a bup 
repository, but it is a standard valid git repo underneath). While 
validating that a repack ran succesfully I executed the command:

 git rev-list --objects --all > rev.list

And got back this:

error: packfile ./objects/pack/pack-d9808b7515419737806d0c621a0a1910f71c5cba.pack cannot be accessed
fatal: missing blob object '27a8cf44da85b958aef2b5074931e7913e08ae95'

Several hours later after successful fsck, and after chasing down trees 
blobs etc, I realized that the problem is too many open files. The hint 
came from ls-tree which lists the correct error (among a lot of spurious 
junk):

 git ls-tree -r c636a5f51d4e > /dev/null

 error: packfile ./objects/pack/pack-d9808b7515419737806d0c621a0a1910f71c5cba.pack cannot be accessed
 error: packfile ./objects/pack/pack-841e375f5e6c793a52fd1a3a2aea0b76219c4cdd.pack cannot be accessed
 error: packfile ./objects/pack/pack-e67d9bf75e0840fc6113170b314d2d5a32cbb45a.pack cannot be accessed
 error: packfile ./objects/pack/pack-b8fd8f083461c391fe6ec396840c328620d912e2.pack cannot be accessed
 error: packfile ./objects/pack/pack-d9808b7515419737806d0c621a0a1910f71c5cba.pack cannot be accessed
 error: packfile ./objects/pack/pack-804e0fadf56e2a165c157ef257620369adeea595.pack cannot be accessed
 error: unable to open object pack directory: ./objects/pack: Too many open files
 error: packfile ./objects/pack/pack-804e0fadf56e2a165c157ef257620369adeea595.pack cannot be accessed
 error: Could not read 32a050cb7e54a1e817d135d25ab251480e8d9e3c

Failure to report the correct message verified with git 1.7.2.5 and 
1.8.2 (debian testing and experimental).

I hope this is sufficient description to address the underlying issue. I 
will keep the un-repacked "many files" repo around just in case you need 
more info/testing (though lowering the ulimit works equally well on 
normal-size repos).

Cheers

             reply	other threads:[~2013-03-03 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03 23:29 Peter Rabbitson [this message]
2013-03-05 15:26 ` [BUG] Incorrect/misleading error when `git rev-list --objects --all` hits the max open files limit 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=20130303232927.GA16606@rabbit.us \
    --to=rabbit@rabbit.us \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.