All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ajay <ajay.dadgas@galaxyweblinks.in>
To: git@vger.kernel.org
Subject: bug reporting
Date: Fri, 26 Sep 2014 19:11:35 +0530	[thread overview]
Message-ID: <54256D0F.4000003@galaxyweblinks.in> (raw)

Hello,

          I have faced a git bug. When I try to clone a git repo it 
shows an error "protocol error: bad pack header".

          This is the full error message which I got while cloning git 
project :

Clone: protocol error: bad pack header
     $ git clone -v --progress 
http://dev.galaxylipl.com:88/galaxygit/privatenovator.git 
/home/lipl/privateschoolinnovator
     Cloning into '/home/lipl/privatenovator'...
     POST git-upload-pack (190 bytes)
     remote: error: Could not read e9a6c4c684a5e8758026e8b0e25867c03332fe7c
     remote: fatal: bad tree object 
e9a6c4c684a5e8758026e8b0e25867c03332fe7c
     remote: aborting due to possible repository corruption on the 
remote side.
     protocol error: bad pack header

I tried everything to resolve this error, I have run some commands on 
server side like :

# git fsck
# git-fsck --full
# git fsck --lost-found
# git repack
# git gc

         But nothing worked for me and the error is still same. I tried 
to find the corrupt file but I was unable to find.

         Please check this issue and provide me proper solution for this.

Thanks & Regards,
Ajay Dadgas

             reply	other threads:[~2014-09-26 13:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 13:41 Ajay [this message]
2014-09-26 23:51 ` bug reporting brian m. carlson
     [not found] <1621111620246345@mail.yandex.ru>
2021-05-05 22:37 ` Bug reporting Alejandro Colomar (man-pages)
     [not found]   ` <1492841620310804@mail.yandex.ru>
2021-05-09 16:40     ` Michael Kerrisk (man-pages)
2021-05-09 17:20       ` Alexander Monakov
2021-05-09 17:58         ` Michael Kerrisk (man-pages)

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=54256D0F.4000003@galaxyweblinks.in \
    --to=ajay.dadgas@galaxyweblinks.in \
    --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.