Output of restic version

PS D:\> .\restic_0.17.0_windows_amd64.exe version
restic 0.17.0 compiled with go1.22.5 on windows/amd64

What backend/service did you use to store the repository?

Local file system

Problem description / Steps to reproduce

I decided to try out Restic, on Windows, for the first time, today, as a way of doing portable back-ups, to a USB drive (5TB, single ExFAT partition), from multiple machines, and tried creating an archive, with:

restic_0.17.0_windows_amd64.exe -v backup -r Archive2 --insecure-no-password C:\Users "D:\Components 1"

Whilst this mostly seemed to "work", in that objects from C:\Users were being collected, and the repository directory was ballooning in size, because of packs being stored, it wasn't until I tried to later access the repository under WSL, and noticed that no actual snapshots were generated, that I realised that something was silently failing, when it came to trying to access files, from the D:\ volume (which ironically, holds Restic, and the repository, itself).

I assumed that this was because of spaces, in the file path, but after trying several permutations, of absolute, and relative paths, and adding/removing paths, running the aforementioned command under PowerShell, I seem to reliably receive the following error:

D:\>restic_0.17.0_windows_amd64.exe -v backup -r Archive2  --insecure-no-password ".\Components 1"
open repository
repository 16e01133 opened (version 2, compression level auto)
found 1 old cache directories in C:\Users\Surface\AppData\Local\restic, run `restic cache --cleanup` to remove them
no parent snapshot found, will read all files
load index files
[0:00] 100.00%  1 / 1 index files loaded
start scan on [.\Components 1]
start backup on [.\Components 1]
scan finished in 0.146s: 6 files, 80.880 KiB
error: nodeFromFileInfo Components 1: get EA failed for path Components 1, with: get file EA failed with: Incorrect function.
Fatal: unable to save snapshot: snapshot is empty

Expected behavior

I'd expect that Restic would make a valiant attempt to access the files, on the ExFAT volume, and add them into a snapshot, and at least give warnings about any files that it can't access, with, or without Administrator privilages.

Actual behavior

As in aforementioned Problem description.

Do you have any idea what may have caused this?

This seems to be related to the way that Restic grovels for file metadata, and I assume it does something, in a way that assumes the use of NTFS, although I have no way of being able to debug this, with native tooling, right now.

Did restic help you today? Did it make you happy in any way?

The logo is definitely cute, at least. The software itself seems pretty promising, as a portable, cross-platform, single-file back-up/archival solution, given that my usual go-to is BorgBackup. :)