git-http-push (git v1.5) problems with DAVLockDB on reiserfs FS

Hi,

I encountered many problems when using a git repository served over
apache/dav on ubuntu 8.04LTS
* versions in use on server:
- kernel 2.6.24
- apache 2.2.8
- git version 1.5.4.3 or 1.6.6.2 (doesn't change anything on server side)

* versions in use on clients
git 1.5.4.3 => causes problem
git 1.6.6.2 => is ok.

With client 1.5, when pushing more than one commit, it fails with this error:

$ git push origin master
Fetching remote heads...
  refs/
  refs/tags/
  refs/heads/
updating 'refs/heads/master'
  from ad49aa06f145c5176f230744eb047f5f132361ab
  to   3e6a3d8c8d3459c67a50bce55718f3b64db96f84
    sending 6 objects
    done
Updating remote server info
error: http-push died with strange error
error: failed to push some refs to
'http://my.domain.tlt/git-tests/project9.git/'

leaving the repository in the middle of the push which is really bad: $ git fsck bad sha1 file: ./objects/1d/881d1c352047547135810123fdc13fb4f8e1db_88cb4b13-a549-445f-b0f1-79aaf746129e bad sha1 file: ./objects/34/6018f9dafe91cb3fce8af1c49863a72c649e2f_88cb4b13-a549-445f-b0f1-79aaf746129e bad sha1 file: ./objects/52/bb16c7a3c44d589a2cfd132c8cc749ad270dd4_88cb4b13-a549-445f-b0f1-79aaf746129e error: HEAD: invalid sha1 pointer 458703bec0ab47149a9b7d70c384581c9cc0d859 error: refs/heads/master does not point to a valid object! notice: No default references dangling commit 3295f15a5de9a2e58a577f9fe949dd7c81f72c6e dangling blob 40f6abca54b4408eedbf4f34116dd99fed8e205d dangling tree 656844a3f994fae1a92e856ac6b3b5cf9925e79a dangling tree 6b3d8fa638d004fe80f5512e025d74533a142859

I finally noticed that this problem only occurs when I have the DAVLockDB file on a reiserfs partition. If I move it on ext3, it's ok. Weird...

Does somebody know which commit version change this behavior between 1.5 and 1.6 ?

-- Fabien

Hi,

On Thu, Feb 18, 2010 at 6:45 PM, Fabien <fabien.ubuntu@gmail.com> wrote:

although nothing might have changed on the server-side, git does a lot of server-side operations via WebDAV, like locking, moving files, etc.

why not just use git 1.6?

Hi,

Tay Ray Chuan wrote:

Yes, I forgot to say the problem is related to locking problems on the server side : Could not LOCK /git-tests/project1.git/info/refs due to a failed precondition (e.g. other locks)

This is why I tested another file system, because I already had problems in the past with reiserfs and locking :)

Yes, but I have to tell that to around 100 contributors ;-) I plan to use a rule in apache to deny access to old versions of git...

-- Fabien