I got passwordless sshfs mounting working OK ...
Code:
sshfs charles@rose:/home ~/mnt/rose:home/
... and then set about optimising it but sshfs rejected some options.
The sshfs documentation (man page and --help output, slightly different), groups command line options by the subsystems it uses:
- iconv
- module (kernel module?)
- fuse
- mount
- ssh
- sshfs (itself)
There are a lot of options so I listed the ones I wanted to try by subsystem ...
- iconv None required
- module
-o rellinks
- fuse
-o intr
-o no_remote_lock
- mount
-o noatime,nodiratime,noiversion
- ssh None required (all set in ~/.ssh/config)
- sshfs
-o reconnect
... and constructed a command:
Code:
sshfs charles@rose:/home ~/mnt/rose:home/ \
-o intr \
-o no_remote_lock \
-o noatime,nodiratime,noiversion \
-o reconnect \
-o rellinks \
Apparently sshfs exits on finding the first options error. Progressively removing the erroneous options generated these errors before the mount worked:
- fuse: unknown option `nodiratime'
- fuse: unknown option `noiversion'
- fuse: unknown option `rellinks'
The first two were not expected because nodiratime and noiversion are listed in the mount man page in the "
FILESYSTEM INDEPENDENT MOUNT OPTIONS" section. AIUI that means all file systems support those options ... ?
The rellinks error was not expected because the documentation says rellinks is not for fuse but for the kernel ... ?
Researching sshfs "How to" pages, issue pages, blogs, bug reports and mailing list archives suggests that the problem sshfs options I used are used little or not at all ... ?
Or I have missed something in how to pass these documented options on the command line ... ?