From: Jeff King <peff@peff.net>
To: Enchanter <ensoul.magazine@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: packfile is unavailable/cannot be accessed
Date: Wed, 6 Apr 2011 11:42:08 -0400 [thread overview]
Message-ID: <20110406154208.GC1864@sigill.intra.peff.net> (raw)
In-Reply-To: <loom.20110406T020617-993@post.gmane.org>
On Wed, Apr 06, 2011 at 12:09:59AM +0000, Enchanter wrote:
> Today I found these errors when I try to pull from remote:
>
> $ git fetch origin
> error: end of packfile
> ./objects/pack/pack-0bb4b0fb14801efb46a7cb9aab64add08620c0b1.pack
> is unavailable error: packfile
> ./objects/pack/pack-0bb4b0fb14801efb46a7cb9aab64add08620c0b1.pack
> cannot be accessed
> error: refs/heads/newGPMC does not point to a valid object!
> error: end of packfile
> ./objects/pack/pack-bbb57cb715f61347809673448e9ab12084277090.pack
> is unavailable
> error: packfile
> ./objects/pack/pack-bbb57cb715f61347809673448e9ab12084277090.pack
> cannot be accessed
> error: end of packfile
> ./objects/pack/pack-bbb57cb715f61347809673448e9ab12084277090.pack
> is unavailable
> error: packfile
> ./objects/pack/pack-bbb57cb715f61347809673448e9ab12084277090.pack
> cannot be accessed
> fatal: failed to read object 8682d5d2ce5bbab82c9020a986d473aa2a97feb8:
> Illegal seek
> fatal: The remote end hung up unexpectedly
>
> Can anyone give me a hit on how to solve this problem?
Looking through the source code, the only way this message can be
generated is if lseek fails on the packfile. It looks like the messages
are coming from the remote end. Where is your remote located? Which
operating system is it running on? Is the repo on an exotic filesystem
that might not support seeking?
-Peff
next prev parent reply other threads:[~2011-04-06 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 0:09 packfile is unavailable/cannot be accessed Enchanter
2011-04-06 15:42 ` Jeff King [this message]
2011-04-07 0:01 ` Enchanter
2011-04-07 0:47 ` Jeff King
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=20110406154208.GC1864@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=ensoul.magazine@gmail.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).