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

[BUG] splitIndex with skipHash corrupts index and crashes status

From
Andy Koppe <andy.koppe@gmail.com>
Date
Nov 7, 2026, 12:11 UTC
Message-ID
<20261107121119.2995843-1-andy.koppe@gmail.com>

With both core.splitIndex and index.skipHash enabled (the latter e.g. via feature.manyFiles), index entries are silently lost or corrupted whenever the shared index is written.

  $ git init -q r && cd r
  $ git config core.splitIndex true
  $ touch foo bar && git add . && git commit -qm init
  $ git config index.skipHash true
  $ git update-index --split-index
  $ git ls-files
  ./
  ./
  $ git status --short
  BUG: wt-status.c:585: multiple renames on the same target? how?
  Aborted (core dumped)

Without the explicit --split-index, this happens once the shared index is rewritten because enough entries have changed.

In a new repository, the first git add writes a shared index, and the added entry is lost straight away:

  $ git init -q r && cd r
  $ git config core.splitIndex true
  $ git config index.skipHash true
  $ touch foo && git add foo
  $ git status --short
  ?? foo
  $ ls .git | grep index
  index
  sharedindex.0000000000000000000000000000000000000000
Note the unexpected null OID.
Seen with v2.56.0 on x86_64 Linux.
Next: Tanga Joris
Message 1 of 5 in “[BUG] splitIndex with skipHash corrupts index and crashes status”
  1. Andy KoppeNov 7, 2026
  2. Tanga JorisNov 7, 2026
  3. Andy KoppeNov 7, 2026
  4. Tanga JorisNov 7, 2026
  5. read-cache: do not skip the hash of the shared indexTanga Joris, Nov 8, 2026

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.