FS#55564 - [sshfs] does not work in /etc/fstab with fuse3 (only with legacy fuse2)
Attached to Project:
Community Packages
Opened by Stefan Majewsky (majewsky) - Saturday, 09 September 2017, 14:18 GMT
Last edited by Anatol Pomozov (anatolik) - Monday, 18 September 2017, 21:22 GMT
Opened by Stefan Majewsky (majewsky) - Saturday, 09 September 2017, 14:18 GMT
Last edited by Anatol Pomozov (anatolik) - Monday, 18 September 2017, 21:22 GMT
|
Details
A long description of this bug is in the first post of
https://bbs.archlinux.org/viewtopic.php?pid=1734157.
The short version is this: If you have an /etc/fstab entry with type "fuse.sshfs", it cannot be mounted with current sshfs-3.2.0-1 and fuse3-3.1.1-1 because /usr/bin/mount.fuse is missing. Adding a symlink at /usr/bin/mount.fuse to /usr/bin/mount.fuse3 makes "mount /path/to/sshfs-based/mount" work. |
This task depends upon
"/usr/bin/mount.fuse" is currently "mount.fuse2". It appears the separation between mount.fuse2 and mount.fuse3 was deliberate by upstream to avoid conflicts [1] (and useful when only sshfs depends on fuse3).
[1] https://github.com/libfuse/libfuse/blob/322536fa059159c0cca2745ba4890827a2b0aac0/ChangeLog.rst#L162
As such, the fuse2/fuse3 packaging is correct, though you could argue for fuse2 to ship "mount.fuse2" and create a symbolic link accordingly.
The mentioned issues with the "fuse3.sshfs" mount type look like an upstream error. I'd suggest you to contact sshfs and/or util-linux (for mount):
https://github.com/libfuse/sshfs/issues
https://github.com/karelzak/util-linux/issues
$ sudo mount /media
/bin/sh: fuse3.sshfs: command not found
When sshfs(1) is used to mount the filesystem, it creates a mount with filesystem type "fuse.sshfs" (without "3").