Michael Eischer

The exit code handling still has to be fixed.

> 2024/07/30 11:26:38 cache/backend.go:165 cache.(*Backend).Load 1211 error loading from cache: This is a typical case of an "error: success" message :-) . > 2024/07/30 11:26:38 restic/cmd_mount.go:159 main.runMount.func1 1211 fuse: ->...

Thanks for the log file. It unfortunately doesn't show what's going on, although it shows that the communication between restic and fuse-t seems to be working properly. At least the...

I've opened an issue at fuse-t maybe they have a clue what might be the problem.

Please give https://github.com/restic/restic/pull/5048 a try. That should fix the mount issues on macOS Sonoma.

> In a separate terminal, I changed into `~/restic`, and then typed `ls -l`. The directory was empty: @damoclark Did you run that command after or before `Now serving the...

> 2024/09/15 11:02:11 restic/cmd_mount.go:160 main.runMount.func1 28 fuse: -> [ID=0x3] Lookup error=ENOENT There should be another line further up in the log that also contains `fuse: `. My guess is that...

I did some tests myself, see https://github.com/macos-fuse-t/fuse-t/issues/61#issuecomment-2433341207 for details. tl;dr https://github.com/restic/restic/pull/5048 works. Whereas, I've had varying success with the different fuse-t versions. > unable to umount (maybe already umounted or...

> The path of the `ENOENT` error lookup is `/`. Is that the last step in constructing the internal representation of the fuse filesystem? No, that is very likely unrelated....

Related to https://github.com/restic/restic/issues/1804 . > And a whole class of weird errors that might bubble up to Restic - how can it apply a consistent view of those to a...