RESTIC: Mounting a backup snapshots throws an error “resource temporarily unavailable”.

[sidney2017]

Hi,

I have installed restic on FreeBSD 13.1 (13.1-RELEASE-p2 FreeBSD 13.1-RELEASE-p2 GENERIC amd64) and also made a first backup.

After that I wanted to mount the repository, but I get an error “resource temporarily unavailable”.

What could be the reason for this?

Apparently, this has also been a topic here before:
https://github.com/bazil/fuse/issues/280
and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265736

Since that was some time ago, I can't imagine that this problem hasn't been solved yet.
Is there anything in particular that I need to be aware of? Am I doing something wrong?

Thanks in advance and kind regards
Sidney2017

#go version
go1.20.3 freebsd/amd64

#restic version
restic 0.15.2 compiled with go1.20.3 on freebsd/amd64

#restic -r /usr/home/restic mount /mnt/restic
enter password for repository:
repository f9779e9c opened (version 2, compression level auto)
Now serving the repository at /mnt/restic
Use another terminal or tool to browse the contents of this folder.
When finished, quit with Ctrl-c here or umount the mountpoint.
resource temporarily unavailable

#kldload fusefs
#kldstat | grep -i fuses

Id Refs Address Size Name
1 1 0xffffffff82d1c000 11cd8 fusefs.ko

 

[nunotex]

Hello,

Something similar on net/rclone.
I'm lost on this subject and I'm gathering all info I can get to open PR at bugs, an upstream issue, etc.

258056 – lang/go118: musn't poll /dev/fuse

bugs.freebsd.org

 

[nunotex]

nice, an existent issue at upstream:

restic mount fails on FreeBSD 13.1 · Issue #4043 · restic/restic

Output of restic version restic 0.14.0 compiled with go1.19.2 on freebsd/amd64 How did you run restic exactly? restic mount /mnt/remote/ parameters are injected via a small python wrapper that crea...

github.com

and go:

os: recent FreeBSD update to sys/fusefs to allow kevents breaks go polling model · Issue #54100 · golang/go

What version of Go are you using (go version)? $ go version go version go1.18.4 freebsd/amd64 Does this issue reproduce with the latest release? Yes, but it's dependent on the FreeBSD release. i.e....

github.com