threads / discuss / 27005

packfile is unavailable/cannot be accessed

Subject: packfile is unavailable/cannot be accessed

## tl;dr

4 messages between Apr 6, 2011 and Apr 7, 2011.

replies: 3people: 2as markdown or json

Enchanter· Apr 6, 2011, 00:09 UTC · lore

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?

Thanks

Jeff King· Apr 6, 2011, 15:42 UTC · re: Enchanter · lore

Re: packfile is unavailable/cannot be accessed

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

Enchanter· Apr 7, 2011, 00:01 UTC · re: Jeff King · lore

Re: packfile is unavailable/cannot be accessed

Jeff King <peff <at> peff.net> writes:

Show 9 quoted lines

> 
> 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
>

Jeff, thanks for you reply.

1. the bare repository is on the windows server
2. One developer use ubuntu with git 1.7.4.1 (Has the error message)
3. Another developer use windows XP with git 1.7.4.msysgit.0 (there's no errors)

Jeff King· Apr 7, 2011, 00:47 UTC · re: Enchanter · lore

Re: packfile is unavailable/cannot be accessed

On Thu, Apr 07, 2011 at 12:01:28AM +0000, Enchanter wrote:

> 1. the bare repository is on the windows server
> 2. One developer use ubuntu with git 1.7.4.1 (Has the error message)
> 3. Another developer use windows XP with git 1.7.4.msysgit.0 (there's no errors)

How are they accessing the bare repo? Directly via a CIFS share, or by git:// running on the Windows server?

-Peff