Alexander Neumann

I've tried to outline and describe what I can imagine doing here: https://gist.github.com/fd0/d24abf8301724988919c80e65aba9b6d There are a few open questions at the end of the document, and it feels to me...

Thank you very much for the comprehensive information! I'm not sure what we'll do, I'm very reluctant to introduce cgo.

A user [reported](https://forum.restic.net/t/cannot-mount-on-macos-with-macfuse-4-x/3338) that restic does not work with osxfuse 4 any more. :(

Hey, thanks for your report! I think this is a bug, we need to handle this corner case a lot better. What happens here is restic tries to access part...

Huh, odd. Files usually don't vanish into thin air from any file system, there should at least be errors in the kernel log... And restic will only make a note...

Odd, indeed. It could also be a bug in restic, but I haven't heard that particular issue recently, especially not with the local backend. But of course I cannot rule...

Huh, interesting, thanks for the report. What happens in the background is that restic creates a lock file (non-exclusive, there may be multiple clients running backup in parallel), then waiting...

Thanks for the feedback

Thanks for the suggestion :)

Hey, thanks for the report. I think you've read about `--quiet` in the changelog, that was a bit unfortunate... It was a workaround for the old version of the archiver...