09-09-2022, 03:00 PM
(This post was last modified: 09-09-2022, 03:01 PM by TheOldPresbyope.
Edit Reason: typo
)
(09-09-2022, 12:27 PM)Tim Curtis Wrote: The 'noserverino' option has come up before and it's on the TODO list to add it to the default SMB mount flags.
I can prolly slip it into the 8.2.0 release.
You can read about the option at the link below. I'm not a Samba expert so I can't say why the option affects your mount. Maybe it has to do with the way Samba is configured on the NAS ??
https://www.samba.org/~ab/output/htmldoc...ifs.8.html
I've been feeding SMB shares to moOde for years as we've moved through many major and minor releases. Servers include a virtual Synology DSM, Samba on various Linux hosts, a stand-alone OpenMediaVault appliance on an SBC, even Windows 7 back in the day. I've never had a problem related to stale file handles.
As I read the Samba docs, though, it appears that setting the noserverino option will be harmless in our application.
With the evolution of the scanning code in moOde, I can now reliably scan for SMB shares on my LAN from all the sources I mentioned above. The only fly in the ointment in my case is that there's no local DNS service on the LAN so when, for example, the scan returns "OMV/Music" I have to hand-edit the share to be "OMV.local/Music" for the connection to succeed. The IP address would work as well, of course. [I'm not prepared to recommend that moOde always use mDNS addresses if they are available, but it's a thought.]
I'm not sure why it's necessary for the OP to force "vers=3". Granted I did my testing a while ago when Tim removed the explicit level set in moOde's default string, but at the time moOde could reliably negotiate a connection with servers configured with various minimum and maximum protocol level settings. Will explore again.
Regards,
Kent