Output of restic version

restic 0.18.0 compiled with go1.24.1 on linux/arm64

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

rclone:protondrive

Problem description / Steps to reproduce

Problem description: On (at least) arm64 - in my case Raspbian on a Raspberry Pi 4 - attempting to start a background sync to a protondrive-backed restic respository will lead to an ENOTTY error and fail, causing the current TTY to be logged out at the same time.

Steps to reproduce

Initialise a repository on a protondrive remote via rclone:

restic -r rclone:protondrive:backups/restic init

Attempt to backup in background:

nohup restic -r rclone:protondrive:backups/restic --verbose backup $HOME/Documents &

Output:

nohup: ignoring input and redirecting stderr to stdout

logout
Connection to HOSTNAME closed.

Contents of nohup.out:

Fatal: unable to open repository at rclone:protondrive:backups/restic: error moving process to background: inappropriate ioctl for device

Expected behavior

Restic should run in the background and dump its output to nohup.out, or wherever it's piped to.

Actual behavior

Restic fails and logs out the current TTY session.

Do you have any idea what may have caused this?

No - it doesn't happen when running the same steps with local media as the backup location, for example. Cause of failure is probably somewhere in the rclone to protondrive or restic to rclone integration.

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

Restic works great for local backups so far.