I’ve been using restic for a few years now, mainly on W10.
NB version:
“restic 0.14.0 compiled with go1.19 on windows/amd64”
This is a pretty basic question, and no-one seems to have asked it: is restic for use on an NTFS-formatted partition?
The reason I ask is because I ran into a problem just now, not with restic, but with rsync in W10’s WSL system.
This rsync command is for mirroring from one NTFS-formatted location to another NTFS-formatted location, both external hard drives.
Here’s how things went:
root@M17A:/mnt/c/WINDOWS/system32# rsync -rtivlHu --delete-before --exclude "Disk images/M17A/Macrium" --ignore-errors "/mnt/f/Backups/" "/mnt/h/Backups/"
building file list ...
rsync: readlink_stat("/mnt/f/Backups/restic/My Documents/data/c3/c360d64de7e422e13a4a858a306e3d99ea39700755b12e3573ff3950cce772f3") failed: Invalid argument (22)
done
...
(NB although it prints “done” this doesn’t in fact stop the rsync process).
But rsync appears to fail with that file. However, that file (and its whole path) doesn’t seem to contain any characters which are illegal for filenames/directory names in NTFS-formatted partitions.
So that made me wonder whether restic (which I think does in fact use rsync internally…) is “OK” if repositories are kept on NTFS partitions.
NB I also found that “WSL 2” can hopefully manage and mount ext4 partitions. But my current setup appears to be “WSL 1” … and when I tried to work out how to upgrade I got TOTALLY lost (although I may try again).
I don’t know that much about rsync’s “error 22” … could it be that the filename (or total file path) is too long for NTFS partitions to handle?
Generally speaking though, is restic in theory totally able to cope with repositories in NTFS partitions?
Later: mysteriously, without me doing any other operations on that repository (i.e. the source on which the copy is made), the problem file appears to have … gone(!). And so the rsync mirror operation above succeeded. Hmmmm!