gc and empty packed-refs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux