Restic takes a long time

[MichaelEischer]

@kapitainsky

Problem is I think that with freshly mounted directories restic considers all content as “new” and rescans every single file (similarly like discussed here on github).

I’m not sure why the same wrong claim gets repeated over and over again. The deviceID is not and never was relevant to decide whether the backup command rescans a file or not.

That github issue is exclusively about unnecessary metadata duplication, but not about unnecessary rescans of files (those are very different things even though the issue completely mixes them up).

@kapitainsky

Not 100% sure if it helps in your specific case but for mounted snapshots I started using rustic which supports ignore-devid option.

Something similar is also available in restic 0.17.0 by setting the feature flag device-id-for-hardlinks via RESTIC_FEATURES=device-id-for-hardlinks=true.

@Imitate8184

shfs on /mnt/user type fuse.shfs

It’s SHFS not SSHFS. Unraid seems to use a homegrown fuse filesystem, however, there appears to be very little documentation for it. I’m wondering how inodes are handled in that filesystem. Are those stable or not? If not, then you must use --ignore-inode.