Closed yarikoptic closed 1 year ago
nope, rerunning gets into the same pickle! @jwodder please instrument code so that if execution of git rm
doesn't succeed and talks about .git/index.lock
, check fuser -v
on that file (or some other command to discover what other process holds it) -- I guess we might need to stop some processes. If they are some git annex --batch'ed processes, then should be a matter of running ds.repo.precommit()
which should stop them all.
FTR: we do .precommit()
in datalad before "rm"
: https://github.com/datalad/datalad/blob/HEAD/datalad/support/gitrepo.py#L1309 .
was addressed by precommit in #292
recent backup failed due to
full output
```shell publish(ok): . (dataset) [refs/heads/git-annex->github:refs/heads/git-annex e4601ea..f42d75a] action summary: publish (ok: 2) fatal: Unable to create '/mnt/backup/dandi/dandisets/000026/.git/index.lock': File exists. Another git process seems to be running in this repository, e.g. an editor opened by 'git commit'. Please make sure all processes are terminated then try again. If it still fails, a git process may have crashed in this repository earlier: remove the file manually to continue. fatal: Unable to create '/mnt/backup/dandi/dandisets/000026/.git/index.lock': File exists. Another git process seems to be running in this repository, e.g. an editor opened by 'git commit'. Please make sure all processes are terminated then try again. If it still fails, a git process may have crashed in this repository earlier: remove the file manually to continue. fatal: Unable to create '/mnt/backup/dandi/dandisets/000026/.git/index.lock': File exists. Another git process seems to be running in this repository, e.g. an editor opened by 'git commit'. Please make sure all processes are terminated then try again. If it still fails, a git process may have crashed in this repository earlier: remove the file manually to continue. 2022-11-02T06:05:12-0400 [ERROR ] backups2datalad: Job failed on inputwhich we didn't encounter before and unfortunately git does not provide us with enough information on what other process locked it. for now I will pretend it didn't happen , reset --hard, clean, and remove lock. And then rerun backup