NFS automount -- How???

Greetings,
I purchased a Mac Mini on the 26th, and have 2 other Linux boxes on the network. The Linux server is set up using SMB and NFS for file sharing, and I can mount the NFS export by issuing a 'mount -t nfs john:/home/jgould mnt'. I have to restart Finder to cause it to show up on the desktop and in the side bar. Is there a way to make the OS auto mount the share on startup (Not that I restart that often) I've searched for an /etc/fstab file, but can't find it. Any ideas would be helpful
Josh

I did what you suggested, and had no errors in the process. After I did i rebooted adn this is waht my mount list looks like:
Danielle:~ jgould$ mount
/dev/disk0s3 on / (local, journaled)
devfs on /dev (local)
fdesc on /dev (union)
<volfs> on /.vol
automount -nsl [137] on /Network (automounted)
automount -fstab [165] on /automount/Servers (automounted)
automount -static [165] on /automount/static (automounted)
/dev/disk1 on /Volumes/SEAQUEST (local, nodev, nosuid, read-only)
And running a mount -a results in this:
Danielle:~ jgould$ mount -a
mount_nfs: /private/var/automount/Users/jgould/mnt: Operation not permitted
I'm at a loss.
Josh

Similar Messages

After Security Update, NFS automount hangs login over LDAP

We currently have a laptop lab in the process of being set up. We have 45 MacBook Pro systems with Snow Leopard 10.6.4 installed. We had set up LDAP authentication for users to log in to our directory server and it worked great over both wired and wireless (WPA2). After installing security update 2010-005, systems hang upon logging in over wireless. We believe the problem is with an NFS automount we set up, because removing the automount allows users to log in successfully over wireless. The NFS is crucial so that users can save data to the server, however, so this is not a solution. Are there any configuration tweaks to undo whats been blocked by the security update?

After installing update 2010-005, I am having issues with my system hanging during startup (stays indefinitely on the grey 'apple' screen, with a spinning icon, and no status or message stating what it is trying to do).
I am able to restart, hold SHIFT, and boot into safe mode, with limited functionality, but have not been able to resolve the issue.
How did you determine that it was hanging on wireless login? (I have not found a log file that states what the system is doing during startup, or why its hanging)
I have searched for issues like this, and most posts recommend removing entries from /Library/Caches and other similar items, but I'm concerned that I might be starting out with a small problem, and then cause a much bigger problem by removing system entries without really knowing what's broken in the first place.
Is there a debug screen during startup, that would tell me what steps its taking? (or a log file?)
I've looked through all of the entries available to the console log review app (apps/utilities/console.app), and was hoping that 'system.log' would tell me what's going on, but so far I'm not seeing anything useful. (there are errors in there, and it looked like there was a crash around the same time as the update was happening, but I'm not seeing any entry during startup that shows what its trying to do, and reveals that its just stuck on that task)
I've run some of the tasks in the 'Snow Leopard cache cleaner' and onyx utilities, but that hasn't fixed my login problem.
Any info you have on further diagnosis, rolling back the update, or anything I should try next, would be greatly appreciated!

Can't Shake NFS Automount, please HELP!

Mac connects directly to cable modem.
Problem? Something keeps grabbing me when I go online... my Mac cannot change it's IP address.
Folder called automount gets created upon reboot.
Network icon - get info - shows the following: Kind of file is Alias. It is located at /Network. Server is nfs://automount%20-nsl%20%5B197.
I've been getting this forever - If I get rid of it, it reappers.
I have no network here, I'm a home user.
My Windoze doesn't have this automount and gets a new IP each time... but my Mac is locked.
Can anyone please help me?
PS - I've tried DHCP renew, it doesn't work at all, nothing happens. My ISP is clueless about this. I believe it is locking onto a static IP but I'm not the one making it do it!

You report that you're connecting the Mac directly to a Motorola Surfboard without a router. What model Surfboard? (There should be a sticker on the bottom) How is the Windows PC connected to the internet? I have a Mottorola Surfboard at home driving a Mac and Pc, but through an Airport Basestation / router. I suspect that putting a basic four-port US$30 router between the modem and the Mac would help. Note that the Motorola Surfboard FAQ notes that multiple computer support requires a separate router. If you just switch the Ethernet cable from the modem between the PC and the Mac, or connect the Mac via Ethernet and the PC via USB, the modem doesn't accept the Mac's MAC (heardware-specific Media Access Code) after grabbing the PC's MAC code on power up. Putting a router between modem and computers and resetting the modem along with restarting the computers will force the modem to grab the router's MAC, and the router will then serve private-network IPs to the attached computers. Any router currrently on the market will also give you a NAT firewall as well; this hardware firewall can safely be used along with the OS X and Windows software firewalls and can greatly increase the security of your computers (especially the Windows one).
Also from the Motorola FAQ:My computer keeps pulling a 169.254.x.x IP address, the modem has been reset and power cycled and the computer is still getting the same IP address, how do I correct this?
Disconnect the Coax cable from the modem and restart it. Once the "Receive" light begins flashing reboot your computer. If the modem and the computer are communicating, the computer will get a 192.168.100.11 IP address (192.168.0.x with the SBG900) from the cable modem. Shut down your computer. Connect the Coax cable to the cable modem, restart it, and wait for the modem to sync up with the cable company. Once the modem is in sync (Power, Receive, Send, On-line are all illuminated) restart the computer. Once the computer has restarted check the IP address. The computer should have a valid IP address from the cable company. Computers attached to the SBG900 will always get a private (192.168.0.x) address regardless of whether or not the SBG900 is registered on the cable system.

How to create NAS nfs automounts in Mavericks

So I had 3 automount nfs shares working in Mavericks last week, but for some odd reason all stopped working along with access to TimeMachine on my NAS and the ability to open disk images.
After some digging I removed my automount modifications to auto_master in /etc and all started to work again... my problem now is how do I now get my 3 automounts to work again so Aperture and iTunes can see their content on my NAS...
I had added this line to auto_master /Volumes/ -auto_share
I had created a flie in /etc called auto_share and this contained the following
Vault
-fstype=nfs,soft,intr,rsize=32768,wsize=32768,noatime,timeo=900,retrans=3,proto= tcp 192.168.128.20:/Vault
Multimedia
-fstype=nfs,soft,intr,rsize=32768,wsize=32768,noatime,timeo=900,retrans=3,proto= tcp 192.168.128.20:/Multimedia
Aperture
-fstype=nfs,soft,intr,rsize=32768,wsize=32768,noatime,timeo=900,retrans=3,proto= tcp 192.168.128.20:/Aperture
This worked and then it stopped...
Any help appreciated
Andrew

Hi Andrew, as promised, here is my login script. Substitute anything in and including <> for your info. Copy/Paste into AppleScript Editor, save as an .app and add to login items for a user. Logout script to follow.
tell application "Terminal"
     try -- See if the NAS is awake, if not, wake it and give it time to appear
          do shell script "ping -c 1 <ip address>"
     on error
          tell application "Terminal"
               try
                    do shell script "/Applications/wol -q -p=7 <mac address>" -- if the NAS supports WOL
                    delay 120 -- give more or less after timing NAS startup time
               end try
          end tell
     end try
     try -- Make the mount points, repeat for how many are needed
          do shell script "mkdir /Volumes/<Dir1>"
          do shell script "mkdir /Volumes/<Dir2>"
     end try
     set success to 0
     repeat 5 times -- try the mounts 5 times, then bomb out
          delay 5
          try -- perform the mounts, change protocol formats as required (e.g. for SMB mounts "smbfs://..."
               do shell script "mount -t afp afp://<user>:<password@<ip address>/<Share1> /Volumes/<Dir1>"
               do shell script "mount -t afp afp://<user>:<password@<ip address>/<Share2> /Volumes/<Dir2>"
               close every window -- close Finder windows that automatically open on mount
               beep
               activate
               with timeout of 43200 seconds -- Display success dialog and wait up to 12 hours (doesn't need that long) for user to click "OK", reason: see last line, leave out if not needed
                    display alert "<Share1> and <Share2> are now available."
               end timeout
               set success to 1
               exit repeat
          on error number errNum
               tell application "Terminal"
                    quit
               end tell
          end try
     end repeat
     if success is not 1 then -- the bomb out section
          beep
          activate
          display alert "Please check that NAS is on then Log Out and Log In again. ( " & errNum & " )"
     end if
     quit
end tell
tell application "<application name>" to quit -- auto-close any apps that you don't want running for this session, without OK message delay above, script will time out and this line won't execute

How do I make nfs automounted volumes visible in Finder?

or, in other words, have opposite option to default nobrowse?
from mount manpage
             nobrowse
                     This option indicates that the mount point should not be visible via the GUI
                     (i.e., appear on the Desktop as a separate volume).
this is edited mount command output from Mac Pro
mac-pro:~ ivarss$ mount
/dev/disk0s2 on / (hfs, local, journaled)
devfs on /dev (devfs, local, nobrowse)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
map autofs_nfs on /Volumes/lto5 (autofs, automounted, nobrowse)
/dev/disk1s2 on /Volumes/VFS HDD 0122 (hfs, local, nodev, nosuid, journaled, noowners)
varaklani:/nfs on /Volumes/nfs/faili (nfs, nodev, nosuid, automounted, nobrowse)
thanks!
shpokas

Well, when you add a component, it's size is 0,0 and it is located at the top left corner (0,0 point of its parent container). When you call pack(), the components are resized, and their placement is set.
So what you did wrong is that you're trying to repaint the panel1 - therefore panel2 never appears, since its dimension is 0,0.
THere's a solution though. Call the validate method of the container you add the component to - that is, jPanel1.validate() instead of its repaint method. Then panel1 will resize the components it contains. Then its not necessary to call the repaint, it'll be done automatically, because the container's graphics area is not valid any more after the validation.
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
     // Add your handling code here:
     JPanel2 p = new JPanel2();
     jPanel1.add(p);
     // jPanel1.repaint();
     jPanel1.validate();
}

NFS / automount hangs on Solaris 10 SunOS oats 5.10 Generic_125100-07 sun4u

We are running Solaris 10 125100-07 on a SunFire V440.
We host computer services for another department on this host.
The server acts as both an NFS server and an NFS client. We do a lot of cross-mounting in our environment due to the lack of large centralized storage.
This particular machine automounts shares from our Solaris 8, 9 and 10 servers and possibly a few Suse servers, and a NetApp owned by another department.
Every day and a half or so, something happens to either NFS or the automounter, and the machine 'hangs' in that we have NFS requests that never get filled.
Restarting either autofs or the nfs client, or both does not seem to help. The only fix we have found so far is a reboot.
We have throttled NFS_CLIENT_VERSMAX to 3 and set AUTOMOUNT_VERBOSE and AUTOMOUNTD_VERBOSE both to TRUE.
The general failures we see look like this:
May 17 04:44:15 oats nfs: [ID 333984 kern.notice] NFS server grieg not respondin
g still trying
May 17 04:44:15 oats last message repeated 1 time
May 17 04:46:15 oats automountd[392]: [ID 196269 daemon.error] dupreq_nonidemp:
duplicate request in progress
May 17 04:49:57 oats last message repeated 4 times
May 17 04:52:15 oats automountd[392]: [ID 196269 daemon.error] dupreq_nonidemp:
duplicate request in progress
The dupreq_nonidemp messages repeat until we reboot.
The nfs server that does not respond varies from day to day. No other computer on our network complains about it.
This started after we installed 125100-05, and has continued through 125100-07.
As far as I can tell we are up to date on patches:
root@oats # smpatch analyze
No patches required.
Any thoughts?
I was thinking I might back out 125100-XX.
dal
e

Interesting,
we have the same problem on SunOS Generic_118833-36 on V440, V445, V240, V245, but not on an old E420, and not on a T2000.
We upgraded them with patch cluster to Generic_138888-07, but it has not changed anything:
E420 and T2000 are stable, the Fire-Vxxx have problem, each has its own "problem interval": one system 1.5 days, two systems 10 days, one every 3 months.
The problem is: NFS/TCP is suddenly dead. Then all NFS mounts, e.g. a manual mount, is hung with "NFS server not responding". A reboot helps.
We have added proto=udp to the mount options. No more problems since.
Permanent mounts, without Automounter, would certainly work, too.
But IMHO there is nothing wrong with Automounter itself, but the hanging occurs e.g. after 4000 NFS mounts, and Automounter is the enabler for that.

Solaris 10 and NFS/Automount into Solaris 8 Env.

Hello fellow Administrators,
I have recently upgraded my own station to Solaris 10 6/06 update 2 in a Solaris 8 NIS/Automount environment. How ever, i have noticed that my station from time to time 'frezzez' and becomes unresponding. It's as if the system hangs due to some sort of conversation/hand shake with my NIS Server. I have several automounts in my vfstab to my local NIS server.
Question, has anyone else had similair problems/experiances ?
Grateful to any answer that can solve this mystery of mine.
Regards,
Pierre

Hi Robert,
Seems to be working better now and i tried on a user as well and there are no complains yet. In the end i applied the latest Sun Cluster for Sol 10 (not many where applied to the 6/06 update 2) and your small 'hack'.
Thank's a bunch!
Pierre

Deleted These NFS services, how to add them again

svccfg delete -f svc:/network/nfs/status:default
svccfg delete -f svc:/network/nfs/server:default
svccfg delete -f svc:/network/nfs/nlockmgr:default
I need to add these services back again under solaris10 control, how to achive this

These services are NFS Server, Lockd and Statd. You can find them in the SUNWnfscu package, which you can reinstall with #pkgadd.
Btw what's the point of performing actions like svccfg delete ? If you dont want a service running just put it offline, but never (!!!) delete something when you dont know exactly what you are doing.
kind regards
m

Mandatory File Locking In Nfs V3 : How To?

I have a central file say, "central.txt ", mounted on an NFS v3 server. Now I have a minimum of 20 processes wanting to update the "central.txt" file at the same time. To ensure that the entries of this "central.txt" is consistent, I should lock the file before I update it and unlock the file after i update it.
I read is some where that NFS v3 supports only advisory locking. I need a mandatory locking system here. Is there any way I can issue a "mandatory lock" on the central.txt file?
I tried the following without any help.
**NOTE** : I'm using perl to write my script (that uses the central.txt file). It is this script that I run concurrently.
1. flock : doesn't work
2. system ("lockfile -l 10 -s 8 filename); : doesn't work
3. fcntl : doesn't work
4. File::NFSLock : doesn't work
Could any one tell me how to obtain a mandatory lock on a file mounted in NFS v3 and also how to trap any error while locking the file?
Thanks

Can you give more details on your environment? Anyway, you could put them in a database and have that take care of the locking matters if that's feasible in your situation.

Nfs automount group security

Hi I am not the sysadmin, so please bear with me...
I have had E3500 Solaris 2.6 file systems automounted from a couple of dozen Solaris 2.6/8 servers in order to perform Oracle backups to a centralized disk farm for later tape backup. The file systems are owned by oracle:dba and the NFS works great for this purpose!.
That said, is there a way I can control access to the centralized file system so that only the servers I want can automount the directories?. In other words, if someone owns an Ultra-10 on the network, and creates an oracle:dba account they cannot see the directories?
thanks
Dave

1. On the servers that own the file systems to be backed up, specify the NFS share options utilizing the -o ro=client:client: syntax.
example:
Update /etc/dfs/dfstab
share -F nfs -o ro=backupsys1:backupsys2,rw=sysadmin1 /the/filesystem
If you specify ro= or rw= or use them together, then only the hosts you specify can mount the NFS shared files.

I relocated by Centos 5 home directory to an NFS automount, now firefox does not start. What broke?

Fails in both Gnome and KDE. Problem depends on the location of the user home directory. If it is not on the local machine, firefox and thunderbird do not start.

Fails in both Gnome and KDE. Problem depends on the location of the user home directory. If it is not on the local machine, firefox and thunderbird do not start.

Problems automounting NFS

I have an Ubuntu box with NFS server setup. I can mount this in Snow Leopard by opening the terminal and typing:
mount 192.168.1.145:/export/john /Users/john/Server
I can do this as sudo or without and either way I get a folder in my 'Home' folder that I am unable to open as I do not have sufficient permissions BUT also have a disk appear under 'Devices' in finder that I can access. I can read and write to it this way which is great.
If, however, I try exactly the same using Disk Utility and the NFS auto mounter, I only get the entry in my 'Home' folder and am unable to open it due to permissions etc.
Through the terminal method, ls -l gives:
drwxrwxrwx 22 1000 1000 4096 18 Jul 19:36 Server
But with the NFS automount option it is:
dr-xr-xr-x 2 root staff 1 18 Jul 19:56 Server
I am sure that this is something simple about permissions that I am not grasping but I am really stuck! I have read a number of similar posts about this but they all seem to say that a bug was fixed with the upgrade to 10.6.8. I am using 10.6.8.
I really want to get this fixed. I have been using Samba to share but there is, for me, a massive speed difference when transferring files with NFS
Any suggestions would be appreciated.
Thanks

NFS is pretty hard to debug via internet forum because each server is different. Try looking at Apple's Autofs documentation and play around with the actual autofs config files. You might have better luck that way.

Cannot install on automounted device: incorrect "too small size" msg

Hi,
To make a nfs mounted install of StarOffice, I change the directory during setup.
I want to use a directory that is nfs automounted so that everybody will hopefully have access to the install. ( If I ever find out how to do a network install. Can't find the doc on it ?)
When I specify the directory in the setup, a pop-up comes saying there is not enough disk space on it, which is wrong. I do not see why the setup program does not detect automounted partition size and to me this is a bug. It was the same with StarOffice 7 and is still not corrected in 8.0
Regards
Fran��ois

Well, admittedly I do not know the answer on Windows. However, on a Mac you can change any font, including the system fonts. However, you need a free third party utility to do it. Download this and play around:
http://www.bresink.de/osx/0TinkerTool/download.html
I'm having the same problem. I have just purchased
the Macbook Pro and the text display on the screen is
too small from the Menu Bar and drop down windows to
the text on Safari, Firefox etc..
Nothing I can do will make it larger.
I can not find anything on the Apple site to explain
how to make it larger.
Any ideas anyone?
Power Mac Mac OS X (10.4.9)

LDAP automount information

Hello,
after 2 days of work, I write here to find some help.
I have a well configured Leopard Server 10.5.8 which serves users accounts through Open Directory: network users can log to all my Mac OS X clients, home directories are well automounted in /Network/Servers/myserver.com/Users/user1. myserver.com is the server of user1 Home directory.
Now, I want that (let's say) host1 (Leopard Workstation) becomes the Home directory server of user1. So, I created a local account on host1 with network credentials (uid, gid and passwd) and configure /etc/exports to export his home on the network with NFS.
How to put in LDAP server that his home directory is not located on myserver.com but on host1 ? That is when user1 logs on host2, host2 automount host1:/Users/user1 on /Network/Servers/host1/Users/user1 or elsewhere.
Thank you for your help,
Joan

First thing to check is /etc/nsswitch.conf
Next check the directory server access and error logs. In the access log, you should see a search string for the automount info. Make sure that's where your mount info resides. If your automount info resides in a different part of the tree, you can either move the data or define an attribute map in the client config.
Are you using netgroups to provide NFS access? If yes, check that the affected machines are in the appropriate netgroups.
HTH,
Roger S.

Automount home directories from another computer

Hello,
after 2 days of work, I write here to find some help.
I have a well configured Leopard Server 10.5.8 which serves users accounts through Open Directory: network users can log to all my Mac OS X clients, home directories are well automounted in /Network/Servers/myserver.com/Users/user1. myserver.com is the server of user1 Home directory.
Now, I want that (let's say) host1 (Leopard Workstation) becomes the Home directory server of user1. So, I created a local account on host1 with network credentials (uid, gid and passwd) and configure /etc/exports to export his home on the network with NFS.
How to put in LDAP server that his home directory is not located on myserver.com but on host1 ? That is when user1 logs on host2, host2 automount host1:/Users/user1 on /Network/Servers/host1/Users/user1 or elsewhere.
Note: I already test manually the configuration and it works!
1. In WGW, I put /path/user1 as user1's default Home Directory
2. On the client (host2), I manually mount host1:/Users/user1 to /path/user1
3. user1 logs into host2, it works fine.
But I cannot do it for each clients and for each new such user! This is why I want to put this information (for each such user) in LDAP to automatically distribute the information to clients.
Thank you for your help,
Joan

Hello,
after 2 days of work, I write here to find some help.
I have a well configured Leopard Server 10.5.8 which serves users accounts through Open Directory: network users can log to all my Mac OS X clients, home directories are well automounted in /Network/Servers/myserver.com/Users/user1. myserver.com is the server of user1 Home directory.
Now, I want that (let's say) host1 (Leopard Workstation) becomes the Home directory server of user1. So, I created a local account on host1 with network credentials (uid, gid and passwd) and configure /etc/exports to export his home on the network with NFS.
How to put in LDAP server that his home directory is not located on myserver.com but on host1 ? That is when user1 logs on host2, host2 automount host1:/Users/user1 on /Network/Servers/host1/Users/user1 or elsewhere.
Note: I already test manually the configuration and it works!
1. In WGW, I put /path/user1 as user1's default Home Directory
2. On the client (host2), I manually mount host1:/Users/user1 to /path/user1
3. user1 logs into host2, it works fine.
But I cannot do it for each clients and for each new such user! This is why I want to put this information (for each such user) in LDAP to automatically distribute the information to clients.
Thank you for your help,
Joan

NFS automount -- How???

Similar Messages

Maybe you are looking for