There is no way to tell if your SMB connection was optimal or if your experiences could be repeated on someone else’s machines. But this is not Linux Support Communities. Like I said in my post everything appears to be working correctly under the hood this seems to be a bug with Finder.Ĭertainly. Lots of people still use NFS especially in Linux to Linux environments in my case NFS always outperformed SMB shares.
WHAT IS DISK UTILITY NFS MOUNTS MAC
I’m afraid a Mac just isn’t a “business machine” anymore.
I would normally copy it locally, make my changes, and then copy it back to the network. I normally didn’t risk actually opening a file on a network. Quicklook would quickly (no pun intended) bring it to its knees. But event with a well-run SMB Active Directory network, really fast throughput, and fully functional auto mount, the Finder really struggled with network mounts. It was relatively recent, maybe Sierra or High Sierra. I can’t remember the OS version I last used with a network mount. I just wanted to point out that there are very few people doing NFS mounts on Macs these days.Īnd finally, I’m not sure what you expect from this mount. That is a configuration that could be expected to work and be supported. Unfortunately, I would also recommend a real SMB mount, with your machine bound to an Active Directory domain. That should work and you should be able to better gauge how it works at that location.Īs far as network disks go, I would recommend SMB these days, if you can do that. For now, for debugging purposes, I suggest mounting in an existing, non-special directory like /tmp. Since you are having a problem, I would say avoid that location for now. I’m not aware of /Users/Shared being a problem, but then I’ve never heard of anyone using that mount point either. Certain directories more more amenable to NFS mounting than others. It is rarely done anymore and not well supported. That being said, mounting NFS shares is not exactly normal. There have certainly been changes underneath, but Apple has gone to great effort to ensure that you don’t have to deal with those changes in normal circumstances. You should continue to use and look at the file system the same way you always have.
The reason you are seeing the same files in both locations is because there is only one location. It is certainly true that Apple has made the file system layout more complex in Catalina, but it isn’t as complicated as that blog makes it out to be. I have tried pointing iTunes (for example) to the old location or the new location with the same lock-up results.Īny suggestions? Maybe there is a better way to use NFS mounts in Catalina?īe careful about reading random blogs on the internet. But after working in the share for a few minutes, my entire Mac locks up (applications go "not responding" - Finder, Terminal, whatever app is using the NFS mounted data like iTunes, etc).
I can see the files now but in BOTH the new and the old location. so I changed auto_master to mount the NFS share into /System/Volumes/Data/Users/Shared/XXX/ instead. I saw this blog about the changes to Catalina Filesystem.
WHAT IS DISK UTILITY NFS MOUNTS UPGRADE
I would have auto_master mount the NFS shares into /Users/Shared/XXX/ (where XXX is some directory for the share) but, post upgrade to Catalina, I am not able to access the files in that location. I have been using NFS Mounts out of /etc/auto_master for years but it looks like the behavior has changed in Catalina (10.15).
0 kommentar(er)
