I want to share a mounted restic archive on the NAS with samba for Windows and OSX.
I can see all the folders and files, but when I try to open a file I get the message that it does not exist.
Everything works on the NAS without any problems. These are my settings:
Directory rights before the mount:
drwxr-xr-x 2 nas nas 4096 11. Nov 07:17 restic
This is the mount command that you execute as root:
restic -r /mnt/disk6/restic-repo-tools mount --no-default-permissions --allow-other --time-template “2006-01-02_15-04-05” /mnt/restic
Directory rights after the mount:
dr-xr-xr-x 1 root root 0 12. Nov 08:43 restic
path = /mnt/restic/
public = yes
writable = no
comment = smb share
printable = no
guest ok = yes
follow symlinks = yes
wide links = yes
unix extensions = no
I have tried something else. If the backup was created under Linux, I can access the files in the mouted restic archive.
But if I take an archive that was created under Windows (0.16.1) it does not work.
I test it also with my OSX. I create the repo with my Mac and I mount it again on Linux.
That works. Only when I create/fill the repo under Windows do I encounter the problem that I cannot read any files. The directories are displayed and I can also navigate.
This is completely wrong. restic mount should in most regards behave like a regular, read-only filesystem. It may be a bit slow depending on the file access patterns. But you can open / read files just like on a normal filesystem. The mount command also uses a small cache to reduce repeated blob downloads. Opening files and random access (read/seek) work perfectly fine. Otherwise it wouldn’t even be possible to copy files from the FUSE mount.
Snapshots created on Windows contain less metadata than those created on other systems. It’s likely that the Samba problems are related to that.