Michael Eischer
Michael Eischer
If anyone wants to fix this, feel free to open a PR :-) .
> Fatal: unable to open repository at rclone:protondrive:backups/restic: error moving process to background: inappropriate ioctl for device This error is specific to the `rclone` backend. I've managed to reproduce it...
What happens is the following: - when using the rclone or sftp backend, then restic starts the helper program (rclone or ssh, respectively) as a separate process group - restic...
I have a POC in https://github.com/restic/restic/pull/5358 . That should be enough to stop `bash` from exiting. But I still have to think about it a bit more until I'm sure...
Just ignoring the permission error when creating the container, should probably just work. The S3 backend does something similar: https://github.com/restic/restic/blob/8dd95b710e6ba2a267c27f7ad0087d68cad7bdfd/internal/backend/s3/s3.go#L142-L145 If the access token is missing privileges, then creating the...
Ignoring access denied errors when creating the container should be fine. We're already doing something similar in the S3 backend (see https://github.com/restic/restic/blob/bcd5ac34bb2c178605826e0e6ead7ebbccf4fc78/internal/backend/s3/s3.go#L201). So, yes we'd be interested in a PR...
> Makes sense from a safety standpoint when restoring to / As your backup apparently only includes `/home`, `restic restore --delete --target / [...]` would have wiped everything else in...
> however, when I restore the snapshot and specify /home as target I get restored to /home/home > Is there a way to do a restore to /home so I...
> \System Volume Information or > /System Volume Information does NOT work. I would have expected those to work as they are relative paths and restic should just treat them...
~~I know that this has been mentioned in some places, but couldn't find a proper issue. So yes feel free to open one for this discrepancy. This will be very...