Issue #8642 resolved

Errors in our repository

Daniel Galinkin
created an issue

Can someone please take a look at the zahpee repo on zahpee account?

It started throwing errors on remote operations, like this: error: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack does not match index warning: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack cannot be accessed error: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack does not match index warning: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack cannot be accessed error: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack does not match index warning: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack cannot be accessed error: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack does not match index warning: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack cannot be accessed error: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack does not match index warning: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack cannot be accessed error: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack does not match index warning: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack cannot be accessed error: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack does not match index warning: packfile ./objects/pack/pack-b319f5c821f45d1c645994cefa12147e636891eb.pack cannot be accessed

Comments (5)

  1. Nicolas Venegas

    Hi Daniel Galinkin

    I've unpacked the offending packfile and things seem ok:

    $ git fsck --full
    Checking object directories: 100% (256/256), done.
    Checking objects: 100% (191019/191019), done.
    Checking connectivity: 187987, done.
    dangling commit ffd864123c0f0f9056172e8608cd2baabfd89fe6
    

    Can you try again and let me know how it goes, please?

    Cheers

    Nicolas

  2. Daniel Galinkin reporter

    Hi Nicolas,

    I've tried again, and everything seems fine. Should I expect any code/commit losses because of this corruption?

    Anyway, thanks for your time!

    Cheers,

    Daniel

  3. Log in to comment