Summary: | sys-fs/fuse complains about unknown -n flag, which automount is injecting with sshfs automount. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | ciaran <ciaran> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/libfuse/libfuse/pull/716 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
ciaran
2022-12-21 00:59:33 UTC
I will add, that I attempted to build w/ Meson, and configured both with and without disable-mtab set. And I saw no difference in results. Project options Current Value Possible Values Description --------------- ------------- --------------- ----------- disable-mtab false [true, false] Disable and ignore usage of /etc/mtab to test : ------------------------------------------------------- /etc/autofs/... modify auto.master /srv/sshfs/ /etc/autofs/auto.sshfs --ghost,uid=0,gid=0,--timeout=60 add to auto.sshfs test -fstype=fuse.sshfs,allow_other root@127.0.0.1:/root ensure you have a passwordless authorized key for root@localhost mkdir -p /srv/sshfs/test/ should work - sshfs root@127.0.0.1:/root /srv/sshfs/test/ mount -t fuse.sshfs -o uid=0,gid=0,allow_other root@127.0.0.1:/root /srv/sshfs/test [doesn't work for me, via autofs ] (no other manual mounts) ls /srv/sshfs/test/ OR (-n) sshfs root@127.0.0.1:/root -n /srv/sshfs/test/ [ remedy ] cd /usr/src/ git clone git clone https://github.com/pcxmac/libfuse.git cd libfuse mkdir build cd build rc-service autofs stop meson .. ;ninja;meson test;cp lib/libfuse3.so.3.12.0 /usr/lib64; cp util/fusermount3 /usr/bin;cp util/mount.fuse3 /usr/sbin rc-service autofs restart [ does work now ] final addition, for the record mount (automount) does know about -n, but fuse is not coded to handle such a flag. Here is the man page for [mount]'s understanding of -n -n, --no-mtab Mount without writing in /etc/mtab. This is necessary for example when /etc is on a read-only filesystem. Sorry, it's not 100% clear to me what the request is here. Is this a heads up about the upstream PR and a request for us to backport it to fuse in Gentoo? I am filing the bug because it's a real issue for me, I am not sure why its not an issue for other people, although I have seen people complain about it through google search results. So the report is for other people to add in on, and if anyone wants / has the time to confirm the bug exists. I use gentoo/openrc + zfs on root, to be honest SSHFS just does not work for me at least not for about half a year, and this issue could have precipitated due to recent changes in the way autofs uses mtab, how mtab works, etc... What I do know is that one line change, allows fuse to work with the SSHFS in mounting the entry successfully, and flawlessly. I will admit I haven't built a series of tests to see if this breaks anything else, though, I do believe that FUSE will run that flag to a 'null' function, and discard it 'effectively'. The code change has been adopted, and [lib]fuse has been updated. SSHFS works like it should. according to my recent limited testing. |