Page 1 of 1
Forum

Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!

Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.

Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is most likely no translated for the post!





ConnectmeNow - NFS ...
 
Share:
Notifications
Clear all

ConnectmeNow - NFS shares Mounting but empty  

  RSS

(@ajpleblanc)
New Member
Joined: 2 weeks ago
Posts: 2
October 9, 2020 10:29 AM  

I'm using v3.0.7 on a Mac Mini running  High Sierra 10.13.6.   I've got 6 shared folders all residing on a QNAP -431P (fw 4.4.3).  

I've rebooted both the NAS and the mac mini several times.  

The shares appear to mount successfully, however when i open them, they are empty.  I have unmounted and remounted, but the problem persists.  

I ran into this issue prior to using this application when I was trying to use autofs natively in MacOS.  

Can you give me any suggestions in order to clear this up? My hopeful outcome is to have the shares automatically mount as long as the volumes are available from the NAS. 

 

Thanks


ReplyQuote
 Hans
(@hans)
Noble Member Admin
Joined: 7 years ago
Posts: 1542
October 10, 2020 4:37 AM  

Hi Ajpleblanc!

I'm using a QNAP TVS-873 running QTS 4.4.3.1439 (so, I presume almost the same version as you do).
I have not yet experienced any mounting issues like you're describing.

Since the mount seems successful, username/password are fine.
Does the used user account(s) have proper access rights to the content in the share(s)?

* check this on your QNAP under: Control Panel -> Privilege -> Shared Folders -> select the share, and click the "Edit Shared Folder Permission" button (the yellow folder with the blue hand underneath it, the 2nd icon). Make sure the user at least has "read" rights.

Another reason why you may have an empty folder is if the shared folder and the path you use on yoru QNAP are not the same - although this would be unlikely. Best way to try this is by accessing one of the standard shares like "Downloads" or "Multimedia".

What happens when you try to copy a file in the empty share?
Will you see the file again after reboot of Mac/QNAP?
Are you able to find the file on your QNAP through the QNAP user interface (FileStation)?
(usually shares are listed right under your data volume in File Explorer)


ReplyQuote
 Hans
(@hans)
Noble Member Admin
Joined: 7 years ago
Posts: 1542
October 10, 2020 5:22 AM  

I so totally overlooked the "NFS" detail - my apologies for that.

Now, personally I do not use NFS at all. I prefer SMB, since NFS does not really have any user management options (eg. Username and Password are not used). I'd try moving to SMB.

On that note though: I have worked with several CMN users that successfully use NFS. For me to test NFS I had to pay good attention to the settings on my QNAP, and from time to time I did run into issues (my own fault, I made some errors when setting up the shares).


ReplyQuote
(@ajpleblanc)
New Member
Joined: 2 weeks ago
Posts: 2
October 10, 2020 5:29 AM  

@hans

thanks for your reply.  So last night I rebooted the Mac mini again, and when it came back up, the shares worked!  I had run a file system check on the NAS, but other than that I’m not sure why it resolved.  

I had been using SMB, but switched to NFS because I’ve seen articles that it’s got lower overhead and can be faster.  I’ve seen much less buffering when streaming video from the NAS to KODI (running on the Mac Mini)

 

thanks again!


ReplyQuote
 Hans
(@hans)
Noble Member Admin
Joined: 7 years ago
Posts: 1542
October 10, 2020 5:42 AM  

Ah OK, yeah I've read those articles as well, and back in the day I did try that as well. It didn't work better for my setup, so I went back to SMB.
Good to hear it works better for your setup though, and glad to hear your shares are working  👍 

I've played a little with SSHFS (requires OSXFuse on a Mac), and noticed that it is a lot faster than SMB at times - especially when it come to retrieving very long directory lists. However, the effort needed to get that working made me feel it is not worth it for my purposes.

Hearing you say that NFS is faster, made me look at it again ... haha (being curious, always open for faster solutions).
As for SMB overhead; it probably has more overhead indeed. Although SMB3 seems to perform better, it's still not the fastest option. 😊 

When looking at this article we can see that SMB is catching up though, but NFS is still a little bit faster (when both are using a plain, non AES, connection).
I do like to lock certain directories though, so not every user can access private information.
For example guests are allowed to watch my videos, but cannot write/modify the videos and cannot have access to private videos.
NFS isn't supporting this as far as I know from my experiences.

 


ReplyQuote



Share: