Re: packfile is unavailable/cannot be accessed

From: Jeff King <peff@peff.net>
Date: Apr 6, 2011, 15:42 UTC
Message-ID: <20110406154208.GC1864@sigill.intra.peff.net>
In-Reply-To: <loom.20110406T020617-993@post.gmane.org>

On Wed, Apr 06, 2011 at 12:09:59AM +0000, Enchanter wrote:

Show 26 quoted lines

> 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