Unable to write file: Function not implemented on ReFS file system since version 2.48.1

[0xfeeddeadbeef]

After I've updated my Git to v2.48.1.windows.1, the commands git init, git gc and git add (probably many more, I haven't tried) started failing in repositories that reside on ReFS formatted disks.

This problem was not present in previous release 2.47.1(2).

Example:

# edit global.json and try to git add:
> git add ./global.json

error: unable to write file .git/objects/b1/6c1afa0351d335de649b03647d10bdc8a4e023: Function not implemented
error: global.json: failed to insert into database
error: unable to index file 'global.json'
fatal: updating files failed

The same commands still work without problems on NTFS formatted disks. The same commands also work in previous 2.47.1(2) Git version on the same ReFS disks.

And no, disks are not damaged, I tried same commands on two different SSDs, and two different HDDs.

Additional info

OS version: Windows Server 2022 10.0.20348.3207
Some relevant .gitconfig entries:

[core]
    longPaths = true
    symlinks = true
    fscache = true
    commitGraph = true
[rerere]
    enabled = true
    autoUpdate = true
[fetch]
    prune = true
    writeCommitGraph = true
[pack]
    threads = 1
[gc]
    auto = 1
    writeCommitGraph = true
[maintenance]
    auto = true

[dscho]

I use a DevDrive (which is ReFS, I believe) on 10.0.26100.3194 and I do not get this error with git version 2.48.1.windows.1...

Is there maybe any way you can build Git and see what exact function call reports ENOSYS?

[jensver]

I have the same issue with version 2.48.1 on Windows Server 2022 (10.0.20348.3091) when using an ReFS disk.
I tested it on an NTFS disk on the same server, and it works fine. So, the issue occurs only with repositories on an ReFS disk.
For now, the solution was to roll back to version 2.47.1.

[dscho]

I have the same issue with version 2.48.1 on Windows Server 2022 (10.0.20348.3091) when using an ReFS disk.

@jensver so maybe you can build Git and single-step to find out which function call reports ENOSYS? That would probably help resolve the issue much quicker.

For now, the solution was to roll back to version 2.47.1.

If you want to be stuck with that version, that's a fine approach.

[jensver]

@jensver so maybe you can build Git and single-step to find out which function call reports ENOSYS? That would probably help resolve the issue much quicker.

I'm sorry, that's not really my area of expertise.

[dscho]

that's not really my area of expertise.

@jensver sorry to hear that.