>> If you look in the .git directory, is there a file named RENAMED-REF..1? >> I have no idea how you would create such a ref, nor why it would fail to >> lock (perhaps because of the funny name?), but removing it should >> probably clear up your problem at least. >> >> The name "RENAMED-REF" is only used by git during ref renames, and those >> only happen when renaming branches (via "git branch -m") or remotes (via >> "git remote rename"). So presumably the source of the problem is related >> to one of those operations. >> >> -Peff >> > > Thanks Jeff, > > i will take a look if i will be able to find this ref. The problem > though is that i don't remeber doing any renaming of branches or > remote in this repo. Probably somebody did and pushed it to the > mainline where i got it from by pull... I'll tyr to check this out. > > Thanks, > Eugene > Well, I have removed the file "RENAMEDREF..1" and it didn't resolve the problem. But then i made a "find -name REN*" and found another instance in logs folder. Removing this actually resolved the problem with gc. Still - i have no idea how this ref has appeared there as i believe there was no renaming operations done as well as no manual creation of such ref of course... Thanks, Eugene -- 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