Output of restic version

restic 0.18.0 compiled with go1.24.1 on linux/amd64

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

Local (but behind the scenes, it is using SMB or WebDAV via GVfs FUSE mounts).

Problem description / Steps to reproduce

If I use a FUSE mount to make a WebDAV remote locally accessible (I have not yet tried this with a fully remote backend like rclone), I get errors like the following:

$ restic init --repo blarg2 --insecure-no-password
Save(<key/eb4be4df8e>) returned error, retrying after 1.438621768s: chmod myrepo/keys/eb4be4df8e6b3e81bba4072b5f2f126c0e1953f200c04ebffce01ecff0372ba6: operation not supported
Save(<key/eb4be4df8e>) returned error, retrying after 1.99187847s: chmod myrepo/keys/eb4be4df8e6b3e81bba4072b5f2f126c0e1953f200c04ebffce01ecff0372ba6: operation not supported
Save(<key/eb4be4df8e>) returned error, retrying after 4.295487722s: chmod myrepo/keys/eb4be4df8e6b3e81bba4072b5f2f126c0e1953f200c04ebffce01ecff0372ba6: operation not supported

This is new behavior with 0.18.0 (i.e. it does not happen on 0.17.3).

Things to try still:

• Using rclone backend on these

Expected behavior

Not stress about the lack of a functioning chmod on systems that don't really support it.

Actual behavior

The command takes forever while it retries. Not sure if it actually ends after a certain number or not. I get impatient.

Do you have any idea what may have caused this?

I'm guessing restic added some error checking, but maybe it can be relaxed somewhat in these cases.

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

Restic is great. I maintain the backup program Déjà Dup and I have started defaulting to restic instead of our previous backend. It's been going well so far!