Hello!
I noticed that restic mount tries to use fusermount and fails if it can’t find it in $PATH. I was wondering if creating a symlink to fusermount3 is safe or if I should just install FUSE2.
Thanks for the great project!
This issue has recently appeared for me as well and I’m no longer able to mount the repository.
Is there anything that can be done about this? The restic mount command is now totally broken in Fedora 44.
I’m assuming that it’s also broken for other Linux distros.
Fedora 44 user here, I wasn’t seeing the same issue, so went digging.
I’ve got fuse2 and 3 installed side by side on both my Fedora boxes, probably because both were upgraded from F43. I’ve not noticed any problems with that, so that’s one solution.
Symlinking fusermount → fusermount3 also worked fine for me in a cursory test, so that’s probably a better workaround than installing fuse2. Maybe try that and let us know how you get on?
If that works, I expect restic could be updated to use fusermount3 if available.
@PatthewMerry why would your fusermount not be in your $PATH?
@PatthewMerry @Smedley_Butler what is the exact command and error you get?
I did a quick trial on Ubuntu server 24.04.4 LTS with restic 0.18.1 and it works normally.
ResticBackup$ which fusermount
/usr/bin/fusermount
ResticBackup$ fusermount --version
fusermount3 version: 3.14.0
ResticBackup$ ls -l /usr/bin/fusermount
lrwxrwxrwx 1 root root 11 apr 8 2024 /usr/bin/fusermount -> fusermount3*
ResticBackup$ restic -r ST/test.transfer.repo/ mount /tmp/resticmount/
enter password for repository:
repository 0ee0a9d7 opened (version 2, compression level auto)
[0:00] 100.00% 1 / 1 index files loaded
Now serving the repository at /tmp/resticmount/
Use another terminal or tool to browse the contents of this folder.
When finished, quit with Ctrl-c here or umount the mountpoint
ResticBackup$ mount|grep resticmount
restic on /tmp/resticmount type fuse (ro,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/tmp/resticmount$ ls -l
total 0
dr-xr-xr-x 1 ubuntu ubuntu 0 mei 29 12:35 hosts/
dr-xr-xr-x 1 ubuntu ubuntu 0 mei 29 12:35 ids/
dr-xr-xr-x 1 ubuntu ubuntu 0 mei 29 12:35 snapshots/
dr-xr-xr-x 1 ubuntu ubuntu 0 mei 29 12:35 tags/
For me I’m currently running Fedora F44 Silverblue and it appears that with this version I only have fusermount3 installed in /user/bin/.
I have a pinned version of Fedora F43 and when I check that version it shows that it has both /user/bin/fusermount and also /user/bin/fusermount3. With F43 I’m able to mount my repository without any issues.
The command “which fusermount” returns the message that there is no fusermount in my PATH while “which fusermount3” returns /user/bin/fusermount3.
The exact error message that I get when trying to mount my repository in F44 is:
fusermount: exec: “fusermount”: executable file not found in $PATH
I would imagine that the issue is related to this:
@Smedley_Butler i only have fusermount 3.14.0, fusermount is a link to fusermount3, see my previous reply.
Your real problem in Fedora44 is that somehow your fusermount is not found in the $PATH, which is weird since normally an OS takes care of backward compatibility.
The quick fix seems to creat a symbolic link like this:
cd /usr/bin && sudo ln -s fusermount3 fusermount
That should give a response for which fusermount which should allow restic to mount the repo.
p.s. related: Failed to Open Backup: fusermount command required - Fedora Discussion
EDIT : since fusermount3 is released >10yr ago, maybe you should file a ticket on github to get restic mount to look for fusermount3 and potentially use fusermount as last resort, see here related discussion on rclone fusermount3 not found on all systems - fall back to fusermount? · Issue #298 · bazil/fuse · GitHub
I don’t have FUSE2 installed, only FUSE3. I thought the OP made it clear.
I don’t know how backwards compatible fusermount3 is, that is why I am asking if I can get away with making a symlink. My distro of choice does not create one.
Under Ubuntu (24.04 and 26.04 at least), /usr/bin/fusermount is a symlink to /usr/bin/fusermount3 and that seems to work without problems.
edit: now I see that this info is already part of the post above: #5
@PatthewMerry long story short; please try to create the symlink and let us know if it works, it may help @Smedley_Butler too.
On Silverblue I would be a bit careful with cd /usr/bin && sudo ln -s ..., since /usr is meant to be managed by the image/rpm-ostree. If restic only checks PATH, a small wrapper or symlink in /usr/local/bin (or ~/.local/bin if it is in PATH for that command) pointing to /usr/bin/fusermount3 is easier to undo. Then which fusermount should show that path before testing restic mount.
1 Like