From: Allan Wind <allan_wind@lifeintegrity.com>
To: git@vger.kernel.org
Subject: gc and empty packed-refs
Date: Sun, 15 Jun 2008 19:27:12 -0400 [thread overview]
Message-ID: <20080615232712.GA28979@lifeintegrity.com> (raw)
So I ran `git gc` as a user with group write access to my repository, then
noticed that remote clients complaining:
allan@vent:~/var/git/www$ git pull
You asked me to pull without telling me which branch you
...
allan@vent:~/var/git/www$ fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
which appears to be related to the packed-ref file being empty (as well
as info/refs) on the server. I copied the two files from my client to
the server to get things going again. No idea if this is a sane thing
to do, but at least my clients will pull again.
`git fsck` gives me dangling blob files:
dangling blob 9b08c9937daee703d97aa487d258f93ab92eb691
dangling blob 7361898075e647e47c8835320e5481e94d8ef275
dangling blob 359e9687e64d8f7a9fd039131fd733a9726a1bad
dangling blob a64f34e998ae9db80ef8ea33cb30e2486829d308
dangling blob a913d295a26ccda2fac7fc051f2e23400f187035
dangling blob e6773de701ef3b7a9e8c80e2319dcd4629702220
It seems gc is causes corruption.
/Allan
reply other threads:[~2008-06-15 23:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080615232712.GA28979@lifeintegrity.com \
--to=allan_wind@lifeintegrity.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).