From: Andreas Krey <a.krey@gmx.de>
To: git@vger.kernel.org
Subject: Races on ref .lock files?
Date: Fri, 16 Dec 2016 17:47:51 +0100 [thread overview]
Message-ID: <20161216164751.GA12174@inner.h.apk.li> (raw)
Hi all,
We're occasionally seeing a lot of
error: cannot lock ref 'stash-refs/pull-requests/18978/to': Unable to create '/opt/apps/..../repositories/68/stash-refs/pull-requests/18978/to.lock': File exists.
from the server side with fetches as well as pushes. (Bitbucket server.)
What I find strange is that neither the fetches nor the pushes even
touch these refs (but the bitbucket triggers underneath might).
But my question is whether there are race conditions that can cause
such messages in regular operation - they continue with 'If no other git
process is currently running, this probably means a git process crashed
in this repository earlier.' which indicates some level of anticipation.
- Andreas
--
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
next reply other threads:[~2016-12-16 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 16:47 Andreas Krey [this message]
2016-12-16 17:20 ` Races on ref .lock files? Junio C Hamano
2016-12-16 23:34 ` Bryan Turner
2016-12-21 8:33 ` Andreas Krey
2016-12-21 10:00 ` Andreas Krey
2016-12-21 21:08 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161216164751.GA12174@inner.h.apk.li \
--to=a.krey@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).