sshfs + autofs problems, probably because of an ignored # sign (hash mark)
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
sshfs + autofs problems, probably because of an ignored # sign (hash mark)
I have a working installation of sshfs and fuse. It works flawlessly when mounted manually. However using autofs for this mount is a problem. I'm pretty sure its because of a single "#" character that is being ignored in one of the configuration files.
linux daemon 02:07:36 automount[12923]: mount(generic): failed to mount sshfs (type fuse) on /var/autofs/ssh/testing
linux daemon 02:07:36 automount[12923]: >> see `sshfs -h' for usage
linux daemon 02:07:36 automount[12923]: >> missing host
linux daemon 02:07:36 automount[12923]: mount(generic): calling mount -t fuse -s -o rw,nodev,nonempty,noatime,allow_other,max_read=65536,uid=1000,gid=100 sshfs /var/autofs/ssh/testing
linux daemon 02:07:36 automount[12923]: mount(generic): calling mkdir /var/autofs/ssh/testing
linux daemon 02:07:36 automount[12923]: do_mount sshfs /var/autofs/ssh/testing type fuse options rw,nodev,nonempty,noatime,allow_other,max_read=65536,uid=1000,gid=100 using module generic
linux daemon 02:07:36 automount[12923]: parse(sun): core of entry: sshfs
linux daemon 02:07:36 automount[12923]: parse(sun): gathered options: fstype=fuse,rw,nodev,nonempty,noatime,allow_other,max_read=65536,uid=1000,gid=100
linux daemon 02:07:36 automount[12923]: expanded entry: -fstype=fuse,rw,nodev,nonempty,noatime,allow_other,max_read=65536,uid=1000,gid=100:sshfs testing.org:
linux daemon 02:07:36 automount[12923]: lookup(file): testing -> -fstype=fuse,rw,nodev,nonempty,noatime,allow_other,max_read=65536,uid=1000,gid=100:sshfs\ testing.org\:
linux daemon 02:07:36 automount[12923]: lookup(file): looking up testing
linux daemon 02:07:36 automount[12370]: attempting to mount entry /var/autofs/ssh/testing
I bolded the line that caught my attention. It's SUPPOSED to look like this:
Quote:
mount -t fuse -s -o rw,nodev,nonempty,noatime,allow_other,max_read=65536,uid=1000,gid=100 sshfs#testing.org: /var/autofs/ssh/testing
As you can see, its ignoring everything after the pound sign. Even if I "escape it" by using \# which was suggested by a blog I found. Does anyone have any ideas?
Quote:
# uname -a && automount -v && sshfs -V
Linux santo 2.6.24 #1 SMP Sat Jan 26 14:44:34 EST 2008 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
Linux automount version 3.1.7
SSHFS version 1.9
FUSE library version: 2.7.2
fusermount version: 2.7.2
using FUSE kernel interface version 7.8
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.