This might be related to http://blog.bitbucket.org/2014/04/22/were-migrating-repositories-to-new-hardware/ but I'm reporting just to be careful.
We are expecting very slow push and pulls since yesterday. I get two errors, both of them could very well be due to the locked file system. What bothers me is that i get them over several hours while working on the same repo.
First (When pushing 2f63428):
[srz:~/twy/satisfaction2] dev+ ± git push Counting objects: 29, done. Delta compression using up to 4 threads. Compressing objects: 100% (14/14), done. Writing objects: 100% (15/15), 1.99 KiB | 0 bytes/s, done. Total 15 (delta 12), reused 0 (delta 0) fatal: Unable to create '/data/c01/n01/p/vp0256/data/d-824/r-4061824/refs/heads/dev.lock': File exists. If no other git process is currently running, this probably means a git process crashed in this repository earlier. Make sure no other git process is running and remove the file manually to continue. fatal: The remote end hung up unexpectedly
as well as (~ 17:05 GMT+2)
[srz:~/twy/satisfaction2] dev+ ± git push Counting objects: 31, done. Delta compression using up to 4 threads. Compressing objects: 100% (15/15), done. Writing objects: 100% (17/17), 2.11 KiB | 0 bytes/s, done. Total 17 (delta 9), reused 0 (delta 0) error: Ref refs/heads/dev is at 4cecb251f0620bdeb041aa29d2f636ff1d9d9b4a but expected a1d4ee2d7f4c51e362a0ebcb0c01602c59dd7033 remote: error: failed to lock refs/heads/dev To email@example.com:twygmbh/satisfaction2.git ! [remote rejected] dev -> dev (failed to lock)
Pushing twice seems to work.
Kind regards and thanks for the nice service you build and grow.