> Today's release is skipped since my my local repository broke again.
> The release would contain one bugfix.
>
> - aufs: bugfix, ioctl(2) returns ENOTTY instead of EINVAL
> Reported by Stew Benedict.
>
> I am not sure when I can fix my repository. If it succeeds at once, I
> will release the latest aufs2 tommorrow.
Anyone who is familiar with GIT, please help me.
Today, I tried git push as usual, but got errors.
error: packfile
./objects/pack/pack-f3972e40fa541573e9388780100d3fa4b4bb65a2.pack does not
match index
error: packfile
./objects/pack/pack-f3972e40fa541573e9388780100d3fa4b4bb65a2.pack cannot be
accessed
error: refs/heads/aufs2 does not point to a valid object!
error: packfile
./objects/pack/pack-f3972e40fa541573e9388780100d3fa4b4bb65a2.pack does not
match index
error: packfile
./objects/pack/pack-f3972e40fa541573e9388780100d3fa4b4bb65a2.pack cannot be
accessed
error: refs/heads/aufs2-27 does not point to a valid object!
error: packfile
./objects/pack/pack-f3972e40fa541573e9388780100d3fa4b4bb65a2.pack does not
match index
:::
There were several lines saying "refs/heads/<branch_name> does not point
to a valid object!" for every branch I tried pushing.
git status, checkout were fine.
Then I did git gc. It exited silently. And then git fsck. It reported
several dangling objects.
dangling commit 971722ad2126a978e85ea573ccd93d8c73480ebc
dangling blob 7820763c2888679703329f6174914edec988da61
:::
I think those commands had no problem.
Finally I tried "git fsck --lost-found". It doesn't end. It is still
running for two and half hours. Should I wait until tomorrow?
J. R. Okajima
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
