I'd been doing that for years for a local cloud drive and just trying to make NFS work properly for an automated backup system change (just because) and had to give up on it. Instead I'm using SMB and a user mount to the Volumes location by a registered launch agent. So I'm not using NFS or automount at all. It creates many until the system crashes, and if you try to unmount them you have to unmount -f each one until no more mounts of that path exist before you can clean up the folders in Volumes. I've abandoned NFS mount on OSX Catalina due to the issues with continuous disconnect and re-mount that results in multiple listings for active mounts of the same path. Whereas, the single dot self-reference does work (in that case not duplicating Data). Sorry that's a lazy typo in my reply, yes, it would be necessary to have Data listed twice but that does not work on my system, mount refuses to use it (corrected as you mentioned). So, if your Mount point was Data/./Volumes then it would be wrong It needs to be either Data/./Volumes (as you discovered) or Data/./Data/Volumes.
CONNECTMENOW FREE
I KNOW, RIGHT?įeel free to send me large checks and/or high five the I found that using /./Volumes was not working for me on Catalina” This configuration persists the mount across restarts, and creates the mountpoint automatically. there you go! Technically /./Volumes is still /Volumes, but the automounter does not see things that way ) TL DR / Solution:Ĭhange your /etc/auto_nfs config from (this is all one line): /Volumes/my_mount -fstype=nfs,noowners,nolockd,noresvport,hard,bg,intr,rw,tcp,nfc nfs://192.168.1.1:/exports/my_shareįor pre-Catalina: To (this is all one line) /./Volumes/my_mount -fstype=nfs,noowners,nolockd,noresvport,hard,bg,intr,rw,tcp,nfc nfs://192.168.1.1:/exports/my_shareįor Catalina and up: To (this is all one line) /System/Volumes/Data/./Data/Volumes/my_mount -fstype=nfs,noowners,nolockd,noresvport,hard,bg,intr,rw,tcp,nfc nfs://192.168.1.1:/exports/my_shareĪnd re-run the automounter: $ sudo automount -cv will keep you at the root path.įor example: /././././ is still just /īy now, a few of you have already figured it out. When you're at this path, attempting to reach the parent path, via. When you're talking about paths in just about any environment, the root folder is the highest path you can reach, whether it's C:\ (windows) or / (*nix) It's so easy my jaw dropped when I figured it out.īasically, we trick OS X into thinking we're mounting somewhere else. Note that, if you manually create the mount point using mkdir, it will mount.īut, upon restart, OS X removes the mount point, and automounting will fail. $ sudo automount -cvĪutomount: /Volumes/my_mount: mountpoint unavailable This will not work (anymore!) though it "should". Otherwise the automounter will not be able to read the config and fail with a. Make sure you: sudo chmod 644 /etc/auto_nfs
etc/auto_nfs (this is all one line): /Volumes/my_mount -fstype=nfs,noowners,nolockd,noresvport,hard,bg,intr,rw,tcp,nfc nfs://192.168.1.1:/exports/my_share net -hosts -nobrowse,hidefromfinder,nosuid Somewhere along the line, Apple decided allowing mounts directly into /Volumes should not be possible: I have spent quite a bit of time figuring out automounts of NFS shares in OS X.
0 kommentar(er)
