git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Fatal error: commit-graph-chain.lock': File exists.

From
Thomas Braun <thomas.braun@virtuell-zuhause.de>
Date
Jan 23, 2024, 15:01 UTC
Message-ID
<1015793055.437265.1706022071164@ox.hosteurope.de>
Hi,
Since 2.43.0 I'm seeing the following error message when I fetch from a remote:
$LC_ALL=C git fetch --all
remote: Enumerating objects: 446, done.
remote: Counting objects: 100% (446/446), done.
remote: Compressing objects: 100% (135/135), done.
remote: Total 446 (delta 328), reused 415 (delta 311), pack-reused 0
Receiving objects: 100% (446/446), 432.84 KiB | 1.01 MiB/s, done.
Resolving deltas: 100% (328/328), completed with 29 local objects.
From EEE:XXX/YYY
 * [new branch]          bugfix/ZZZ -> origin/ZZZ
 * [new branch]          bugfix/ZZZ -> origin/bugfix/ZZZ
 + 7244c9b68...6dad36582 feature/AAA -> origin/feature/AAA  (forced update)
 + 7ce96b207...7bee890d6 feature/BBB -> origin/feature/BBB  (forced update)
 * [new branch]          feature/CCC -> origin/feature/CCC
   fd8c36a84..2ab4db03d  main                                            -> origin/main
fatal: Unable to create '/DDD/.git/objects/info/commit-graphs/commit-graph-chain.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.

Observations:
- repo and gitforge independent
- only happens when fetch.writeCommitGraph is turned on
- git gc cleans up the stale lock file
- I think this is only happening when multiple branches on the remote have changed
I do have protocol.version set to 2.
I tried replicating the issue with an example but failed so far.
Does that ring a bell somewhere? Where should I start poking?

Thanks, Thomas

[System Info] git Version: git version 2.43.0 cpu: x86_64 built from commit: 564d0252ca632e0264ed670534a51d18a689ef5d sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh uname: Linux 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 Compiler Info: gnuc: 12.2 libc Info: glibc: 2.36 $SHELL (typically, interactive shell): /bin/bash

Message 1 of 1 in “Fatal error: commit-graph-chain.lock': File exists.”
  1. Thomas BraunJan 23, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.