{"id":2354,"date":"2019-10-17T20:21:40","date_gmt":"2019-10-18T03:21:40","guid":{"rendered":"https:\/\/www.fkylewright.com\/?p=2354"},"modified":"2020-11-19T10:23:42","modified_gmt":"2020-11-19T18:23:42","slug":"macos-catalina-10-15-autofs-mount-point-changes","status":"publish","type":"post","link":"https:\/\/www.fkylewright.com\/wordpress\/2019\/10\/macos-catalina-10-15-autofs-mount-point-changes\/","title":{"rendered":"macOS Catalina 10.15 autofs mount point changes"},"content":{"rendered":"\n

After upgrading to macOS Catalina 10.15, your previously working autofs mountpoints may need to be updated with Catalina’s new filesystem structure.<\/p>\n\n\n\n\n\n\n\n

In this example, I was previously mounting NFS shares from my local NAS to a folder named “Nas” in \/Users\/me. In Catalina, your data moves to a separate volume<\/a> from the operating system files. (You can verify this in Disk Utility.)<\/p>\n\n\n\n

\"\"
New “Data” mount point in Disk Utiility – Catalina 10.15<\/figcaption><\/figure>\n\n\n\n

So from the perspective of autofs, your previous mount points may no longer exist at the previous location. In my case, the \/Users directory moves to \/System\/Volumes\/Data\/Users.<\/p>\n\n\n\n

To fix my \/etc\/auto_nas file, I simply prepended each mount point with \/System\/Volumes\/Data<\/strong>:<\/p>\n\n\n\n

# Media share\n\/System\/Volumes\/Data\/Users\/me\/Nas\/media     -fstype=nfs,noowners,noresvport,hard,bg,intr,rw,tcp,rdirplus,rsize=65536,wsize=65536,readahead=128 nfs:\/\/my-nas:\/mnt\/Pool1\/media\n\n# Storage share\n\/System\/Volumes\/Data\/Users\/me\/Nas\/storage     -fstype=nfs,noowners,noresvport,hard,bg,intr,rw,tcp,rdirplus,rsize=65536,wsize=65536,readahead=128 nfs:\/\/my-nas:\/mnt\/Pool1\/storage\n\n# Archives share\n\/System\/Volumes\/Data\/Users\/me\/Nas\/archives     -fstype=nfs,noowners,noresvport,hard,bg,intr,rw,tcp,rdirplus,rsize=65536,wsize=65536,readahead=128 nfs:\/\/my-nas:\/mnt\/Pool2\/archives<\/code><\/pre>\n\n\n\n
With your mountpoints corrected, save the file, run the automount command (to flush the cache and reload \/etc\/auto_master), and get back to enjoying the new OS!<\/p>\n\n\n\n
sudo automount -vc<\/code><\/pre>\n\n\n\n
If automount completes successfully, but does not confirm that it mounted your shares, you may need to update your automount master mapping file (\/etc\/auto_master) as well<\/a>.<\/p>\n\n\n\n
UPDATE (2020-02-01)<\/strong><\/h2>\n\n\n\n
A word of caution about using a mount point in your Users directory<\/h3>\n\n\n\n
While automount points inside \/System\/Volumes\/Data\/Users\/<you>\/  automount successfully, you may encounter a peculiar issue in Catalina where the mappings duplicate over time (seemingly each time they get re-mounted by autofs), and CPU utilization increases to the point of system instability. If you run the mount<\/em> command, it will report any duplicates, even though you will only see one instance of the mount point in Finder. When the duplication occurs, the automountd process will consume significantly more CPU cycles than it normally would.<\/p>\n\n\n\n
The solution is frustratingly simple: move your automounts outside of the \/System\/Volumes\/Data\/Users\/ directory. After struggling with this for months, I moved my mount points to \/System\/Volumes\/Data\/Nas and everything went back to normal (or at least, to how it behaved pre-Catalina).<\/p>\n\n\n\n
Relevant threads from discussions.apple.com:<\/p>\n\n\n\n