cross platform virtual file systems tend not to fully support platform specific metadata like permission bits.
rclone seems to support chmod by just ignoring it without thowing an error.
fuse, which icedrive uses i think, looks to complain as in your error msg.
a very quick look at restic, they suggest rclone access, icedrive would be the same. icedrive i think does support rclone/webdav but it seems to be throttled (see other posts) so you may not have a good experience.
you may get better advice on restic forums.
Thank you. After much experimentation, I have established that restic cannot work with repositories directly on Icedrive’s fuse mounts in any way, whether it’s for repo creation, checking, inspecting, or restoring.
However, you can create a restic repo locally and rclone it to Icedrive. You then need to download it locally again if you want to check/inspect/restore from it.
I’ve found Icedrive’s WebDAV to handle the uploading of existing restic repos quite well. I think it’s because restic packages data in medium-size chunks, so you avoid the problems that usually arise when you try to rclone lots of small files or very large tarballs to Icedrive. Moreover, because restic repos are encrypted, you can put them in the unencrypted part of Icedrive for slightly better upload speeds.
What I do is use a TrueNAS server as a waystation. I back up data to the NAS using restic, and then the NAS pushes the restic repos to Icedrive using Rclone sync as a cronjob. I keep ~3TB worth of data backed up in this way, and so far I’ve not had any problems.
