This discussion is archived
16444 Views 3 Replies Latest reply: Sep 10, 2009 5:10 PM by Mike Mackovitch
Currently Being ModeratedSep 2, 2009 4:06 PM (in response to Warren Racz)Hi Warren,
I too lost my NFS automounts after the upgrade to 10.6. After a little digging, I found out that I needed to re-add them using Disk Utility, and after a little more digging, discovered that I needed to flush the automountd cache to get the changes to apply:
$ sudo automount -vc
Automount is working now. Not sure if this addresses your issue but HTH.
Currently Being ModeratedSep 4, 2009 6:32 AM (in response to Warren Racz)Turns out there is already a mount on /home (although an empty filesystem) through the automount configuration. I would not have expected mount_nfs to allow an additional mount... By changing to mount directly to another path my problem went away. Alternatively I should be able to remove the /home automount through the automount configuration files, but I would rather not mess with that.MacMini, Mac OS X (10.6)
Currently Being ModeratedSep 10, 2009 5:10 PM (in response to Warren Racz)Yes, the /home automount map is a default that got picked up when autofs was ported from Solaris to Mac OS X. It was there in 10.5 too.
As to why NFS allowed a mount on top of another mount, well... that's just how it works. Mounts are made on directories and there's no restriction on which directories. So, it can be the root directory of some other mount.... of any file system type. This is actually how autofs works a lot of the time. It mounts an autofs file system on the directory where something is to be automounted and then once something tries to access the file system it (auto)mounts the real file system on top of the "trigger" autofs mount.
There is actually a check in the mount(8) command that checks to see if you are trying to mount the same NFS file system on the same path and it disallows that (because that's probably never something you'd want to do intentionally).
I would recommend using mount(8) instead of mount_nfs(8) - it's shorter to type and you get extra benefits like that. Also the '-X' command line flag form of mount_nfs options are deprecated. You should use the "-o option" form instead (e.g. instead of "-i,-s,-w=32768,-r=32768" you would use "intr,soft,wsize=32768,rsize=32768").
Oh, and the system also requires that the directory being mounted on is owned by the user doing the mount (or the mount is being done by root). So, I wouldn't have expected you to be able to mount on /home unless you were doing the mount as root.