Re: repository corruption when pushing commits to a repository running 'git gc --prune='
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Oct 14, 2015, 18:46 UTC
- Message-ID
- <vpqbnc18ezo.fsf@grenoble-inp.fr>
- In-Reply-To
- <561E5C5B.3090207@alcatel-lucent.com>
Jan Smets <jan.smets@alcatel-lucent.com> writes:
Show 6 quoted lines
> 2) > > remote: error: unable to write sha1 filename > objects/05/cdb51bb0ea3e229734a4b1bddd5ec70fbc65ed: No such file or > directory > remote: fatal: failed to write object
If I read correctly, this happens when we move the temp file to its permanent position.
This looks like a race between deleting objects/05/ and creating objects/05/cdb51bb0ea3e229734a4b1bddd5ec70fbc65ed.
I don't understand how this is possible, since the temporary file and the final one are in the same directory, so deleting the directory should fail.
What am I missing?
-- Matthieu Moy http://www-verimag.imag.fr/~moy/