Static NFS Mounts

Running OS X 10.5 Server
I have found that I can mount a NFS export via the automount system through the auto_* configuration files in /etc. As I understand it automount will mount the share on access and unmount it after a period of inactivity.
1. Is there another way to "statically" mount a NFS volume similar to Linux's /etc/fstab or Solaris's /etc/vfstab? I don't want this unmounted, ever. Back to Google for now....
2. If I edit /etc/autofs.conf option AUTOMOUNT_TIMEOUT and set it to 0 will it leave all mounts up after first access? If not, what is the valid range for this parameter?

I have seen this a couple times now. Can you explain why the Directory Utility is the place for something like this? As I understood it this utility/application is for working with LDAP directories not file system directories.
Also, I believe that Directory Utility basically is imputing these mounts into automount which means they become unmounted after X seconds as defined in autofs.conf We have a cron job that needs to access data on the mount once a day. If fails however because it gets unmounted. I have considered putting a "cd /PATH &&" before my job but that seems to be a bit of a hack.
I'd really like to just mount the export and have it remain regardless of what automount wants to do. Surely that is possible.

Similar Messages

Removing NFS mounts after upgrade

In Tiger, I had set up a number of static NFS mounts to a Linux server using NetInfo. After upgrading to Leopard, these static links are no longer working, but the newly created automounts using Directory Utility work fine. I've been trying to remove the old entries using dscl without success. I have a number of entries in /Local/Default/Mounts, eg:
$ dscl localhost -read /Local/Default/Mounts/doobage:\/home\/michael
dsAttrTypeNative:type: nfs
AppleMetaNodeLocation: /Local/Default
GeneratedUID: B719E4FA-33F7-449A-AD63-0452515F0FF2
RecordName: doobage:/home/michael
RecordType: dsRecTypeStandard:Mounts
VFSLinkDir: /server/michael
I've tried deleting these using the dscl -delete command, eg:
$ sudo dscl localhost -delete /Local/Default/Mounts/doobage:\/home\/michael
Password:
delete: Invalid Path
<dscl_cmd> DS Error: -14009 (eDSUnknownNodeName)
I suspect that I'm simply using the wrong key name, however, there aren't any examples of deletion in the dscl man page. Can someone please point out where I'm going wrong?
Thanks,
-Michael

Try to escape the Slash with a double backslash.
Message was edited by: sica187

Nfs mount created with Netinfo not shown by Directory Utility in Leopard

On TIger I used to mount dynamically a few directories using NFS.
To do so, I used NetInfo.
I have upgraded to Leopard and the mounted directories
are still working, although Netinfo is not present anymore.
I was expecting to see these mount points and
modify them using Directory Utility, which has substituted Netinfo.
But they are not even shown in the Mount panel of Directory Utility.
Is there a way to see and modify NFS mount point previously
created by NetInfo with the new Directory Utility?

Thank you very much! I was able to recreate the static automount that I had previously had. I just had to create the "mounts" directory in /var/db/dslocal/nodes/Default/ and then I saved the following text as a .plist file within "mounts".
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>dir</key>
<array>
<string>/Network/Backups</string>
</array>
<key>generateduid</key>
<array>
<string>0000000-0000-0000-0000-000000000000</string>
</array>
<key>name</key>
<array>
<string>server:/Backups</string>
</array>
<key>opts</key>
<array>
<string>url==afp://;AUTH=NO%20USER%[email protected]/Backups</string>
</array>
<key>vfstype</key>
<array>
<string>url</string>
</array>
</dict>
</plist>
I don't think the specific name of the .plist file matters, or the value for "generateduid". I'm listing all this info assuming that someone out there might care.
I assume this would work for SMB shares also... if SMB worked, which it hasn't on my system since I installed leopard.

Since update to 10.4.10 NFS-mounts stopped mounting

Since the update to 10.4.10 (with or without the security update, didn't matter) my NFS-mounts from a Linux-machine via a WLAN-router and Airport to my MacBook Pro.
It did work, although apple-typically unreliable, until the 10.4.10 update.
rpcinfo -p machine shows:
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 1 udp 797 mountd
100005 1 tcp 800 mountd
100005 2 udp 797 mountd
100005 2 tcp 800 mountd
100005 3 udp 797 mountd
100005 3 tcp 800 mountd
schowmount -e machine:
Exports list on dream:
/var/mnt/hdd/Bilder 192.168.233.9/255.255.255.0
/var/mnt/hdd/Tools 192.168.233.9/255.255.255.0
/var/mnt/hdd/movie 192.168.233.9/255.255.255.0
/var/mnt/hdd/Musik 192.168.233.9/255.255.255.0
/hdd/usbstick 192.168.233.9/255.255.255.0
showmount -d machine:
Directories on dream:
/var/mnt/hdd/Bilder
/var/mnt/hdd/Musik
/var/mnt/hdd/movie
192.168.233.9/255.255.255.0
Therefore everything looks ok at the Linux-side, another Linux-machine is able to mount the shares without problems.
The console.log shows:
NFS Portmap: RPC: Program not registered
NFS Portmap: RPC: Program not registered
Jul 15 18:11:50 alu automount[280]: Attempt to mount /automount/Servers/dream/hdd/Musik returned 1 (Operation not permitted)
Jul 15 18:11:50 alu automount[280]: Attempt to mount /automount/Servers/dream/hdd/Bilder returned 1 (Operation not permitted)
Jul 15 18:11:50 alu automount[280]: Attempt to mount /automount/Servers/dream/hdd/Tools returned 1 (Operation not permitted)
Jul 15 18:11:50 alu automount[280]: Attempt to mount /automount/Servers/dream/hdd/movie returned 1 (Operation not permitted)
NFS Portmap: RPC: Program not registered
NFS Portmap: RPC: Program not registered
[...Masses of those lines]
NFS Portmap: RPC: Program not registered
2007-07-15 18:14:55.992 NetInfo Manager[499] * -[NSCFString substringFromIndex:]: Range or index out of bounds
NFS Portmap: RPC: Program not registered
NFS Portmap: RPC: Program not registered
NFS Portmap: RPC: Program not registered
NFS Portmap: RPC: Program not registered
[.... masses of those lines]
I tried with NFS Manager - no luck.
I checked the Netinfo-DB - no luck.
I rebooted the MacBook Pro - no change.
I rebooted the Linuxmachine - no change.
I typed "mount -t nfs ..." into a terminal - no luck.
It is working with Linux - what prevents Apple to get it to work, too?

This error appeared once and never again since.
But NFS-mounts still fail. A friends Titanium, still on 10.4.9, has the normal problems with airport-connection-stability and believed-server-connection-losses but it connects like a charm to that server the Aluminium doesn't like.
I reinstalled 10.4.10, rebooted several times, repaird permissions, searched system.log and console.log but couldn't find a message pointing to a problem (with the exception of a message about a failing startup of my flying butress firewall.
Here you have the latest system.log (deleted some lines for security reasons only):
Jul 16 16:35:22 alu SystemStarter[1322]: authentication service (1332) did not complete successfully
Jul 16 16:35:22 alu SystemStarter[1322]: Printing Services (1325) did not complete successfully
Jul 16 16:35:24 alu Parallels: Unloading Network module...
Jul 16 16:35:24 alu Parallels: Unloading ConnectUSB module...
Jul 16 16:35:24 alu Parallels: Unloading Monitor module...
Jul 16 16:35:28 alu SystemStarter[1322]: BrickHouse Firewall (1338) did not complete successfully
Jul 16 16:35:29 alu SystemStarter[1322]: The following StartupItems failed to properly start:
Jul 16 16:35:29 alu SystemStarter[1322]: /System/Library/StartupItems/AuthServer
Jul 16 16:35:29 alu SystemStarter[1322]: - execution of Startup script failed
Jul 16 16:35:29 alu SystemStarter[1322]: /System/Library/StartupItems/PrintingServices
Jul 16 16:39:57 localhost kernel[0]: hi mem tramps at 0xffe00000
Jul 16 16:39:58 localhost kernel[0]: PAE enabled
Jul 16 16:39:58 localhost kernel[0]: standard timeslicing quantum is 10000 us
Jul 16 16:39:58 localhost kernel[0]: vmpagebootstrap: 254317 free pages
Jul 16 16:39:58 localhost kernel[0]: migtable_maxdispl = 71
Jul 16 16:39:58 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jul 16 16:39:58 localhost kernel[0]: 89 prelinked modules
Jul 16 16:39:58 localhost kernel[0]: ACPI CA 20060421
Jul 16 16:39:58 localhost kernel[0]: AppleIntelCPUPowerManagement: ready
Jul 16 16:39:58 localhost kernel[0]: AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
Jul 16 16:39:58 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
Jul 16 16:39:58 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jul 16 16:39:58 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Jul 16 16:39:58 localhost kernel[0]: using 5242 buffer headers and 4096 cluster IO buffer headers
Jul 16 16:39:58 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jul 16 16:39:58 localhost kernel[0]: Started CPU 01
Jul 16 16:39:58 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Jul 16 16:39:58 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Jul 16 16:39:58 localhost kernel[0]: Security auditing service present
Jul 16 16:39:58 localhost kernel[0]: BSM auditing present
Jul 16 16:39:58 localhost kernel[0]: disabled
Jul 16 16:39:58 localhost kernel[0]: rooting via boot-uuid from /chosen: 4EF96DEE-9FCF-4476-AD53-58BEA0AA953E
Jul 16 16:39:58 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Jul 16 16:39:58 localhost kernel[0]: USB caused wake event (EHCI)
Jul 16 16:39:58 localhost kernel[0]: FireWire (OHCI) Lucent ID 5811 PCI now active, GUID 0016cbfffe66af32; max speed s400.
Jul 16 16:39:58 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT2 @2/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDri ver/FUJITSU MHV2100BH Media/IOGUIDPartitionScheme/Customer@2
Jul 16 16:39:58 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Jul 16 16:39:59 localhost kernel[0]: CSRHIDTransitionDriver::probe:
Jul 16 16:39:59 localhost kernel[0]: CSRHIDTransitionDriver::start before command
Jul 16 16:39:59 localhost kernel[0]: CSRHIDTransitionDriver::stop
Jul 16 16:39:59 localhost kernel[0]: IOBluetoothHCIController::start Idle Timer Stopped
Jul 16 16:39:59 localhost kernel[0]: Jettisoning kernel linker.
Jul 16 16:39:59 localhost kernel[0]: Resetting IOCatalogue.
Jul 16 16:39:59 localhost kernel[0]: display: family specific matching fails
Jul 16 16:39:59 localhost kernel[0]: Matching service count = 0
Jul 16 16:39:59 localhost kernel[0]: Matching service count = 21
Jul 16 16:39:59 localhost kernel[0]: Matching service count = 21
Jul 16 16:39:59 localhost kernel[0]: Matching service count = 21
Jul 16 16:39:59 localhost kernel[0]: Matching service count = 21
Jul 16 16:39:59 localhost kernel[0]: Matching service count = 21
Jul 16 16:39:59 localhost kernel[0]: display: family specific matching fails
Jul 16 16:39:59 localhost kernel[0]: Previous Shutdown Cause: 0
Jul 16 16:39:59 localhost kernel[0]: ath_attach: devid 0x1c
Jul 16 16:39:59 localhost kernel[0]: mac 10.3 phy 6.1 radio 10.2
Jul 16 16:39:59 localhost kernel[0]: IPv6 packet filtering initialized, default to accept, logging disabled
Jul 16 16:40:00 localhost lookupd[47]: lookupd (version 369.6) starting - Mon Jul 16 16:40:00 2007
Jul 16 16:40:03 localhost DirectoryService[55]: Launched version 2.1 (v353.6)
Jul 16 16:40:05 localhost diskarbitrationd[45]: disk0s2 hfs 9AC36BC8-2C3E-3282-B08D-9C22EC354E35 Alu HD /
Jul 16 16:40:07 localhost kernel[0]: yukonosx: Ethernet address 00:xx:xx:xx:xx - deleted
Jul 16 16:40:07 localhost mDNSResponder: Couldn't read user-specified Computer Name; using default “Macintosh-00.........” instead
Jul 16 16:40:07 localhost kernel[0]: AirPort_Athr5424ab: Ethernet address 00:xx:xx:xx:xx - deleted
Jul 16 16:40:07 localhost mDNSResponder: Couldn't read user-specified local hostname; using default “Macintosh-00..........” instead
Jul 16 16:40:08 localhost mDNSResponder: Adding browse domain local.
Jul 16 16:40:09 localhost lookupd[70]: lookupd (version 369.6) starting - Mon Jul 16 16:40:09 2007
Jul 16 16:40:09 localhost configd[43]: AppleTalk startup
Jul 16 16:40:09 alu configd[43]: setting hostname to "alu.local"
Jul 16 16:40:13 alu kernel[0]: Registering For 802.11 Events
Jul 16 16:40:13 alu kernel[0]: [HCIController][setupHardware] AFH Is Supported
Jul 16 16:40:15 alu configd[43]: AppleTalk startup complete
Jul 16 16:40:15 alu configd[43]: AppleTalk shutdown
Jul 16 16:40:15 alu configd[43]: AppleTalk shutdown complete
Jul 16 16:40:18 alu configd[43]: AppleTalk startup
Jul 16 16:40:20 alu mDNSResponder: getifaddrs ifa_netmask for fw0(7) Flags 8863 Family 2 169.254.113.87 has different family: 0
Jul 16 16:40:20 alu mDNSResponder: SetupAddr invalid sa_family 0
Jul 16 16:40:23 alu SystemStarter[51]: BrickHouse Firewall (102) did not complete successfully
Jul 16 16:40:27 alu configd[43]: AppleTalk startup complete
Jul 16 16:40:29 alu configd[43]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Jul 16 16:40:29 alu configd[43]: posting notification com.apple.system.config.network_change
Jul 16 16:40:29 alu lookupd[169]: lookupd (version 369.6) starting - Mon Jul 16 16:40:29 2007
Jul 16 16:40:31 alu mDNSResponder: getifaddrs ifa_netmask for fw0(7) Flags 8863 Family 2 169.254.113.87 has different family: 0
Jul 16 16:40:31 alu mDNSResponder: SetupAddr invalid sa_family 0
Jul 16 16:40:31 alu /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Jul 16 16:40:31 alu SystemStarter[51]: The following StartupItems failed to properly start:
Jul 16 16:40:31 alu SystemStarter[51]: /Library/StartupItems/Firewall
Jul 16 16:40:31 alu SystemStarter[51]: - execution of Startup script failed
Jul 16 16:40:33 alu loginwindow[182]: Login Window Started Security Agent
Jul 16 16:40:48 alu configd[43]: target=enable-network: disabled
Jul 16 16:44:14 alu /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Currently connected to network WZ
Jul 16 16:45:40 alu automount[222]: Can't get NFS_V3/TCP port for dream
Jul 16 16:45:40 alu automount[222]: Can't get NFS_V2/TCP port for dream
Jul 16 16:45:40 alu automount[222]: Attempt to mount /automount/static/mnt returned 1 (Operation not permitted)

Vi error on nfs mount; E212: Can't open file for writing

Hi all,
I've setup a umask of 0 for testing on both NFS client (Centos 5.2) and NFS server (OSX 10.5.5 server).
I can create files as one user and edit/save out as another user w/o issue when directly logged into the server via ARD.
However, when I attempt the same from an NFS mount on a client machine, even as root I get the following error using vi;
"file" E212: Can't open file for writing
Looking at the system.log file on the server, I see;
kernel[0]: add_fsevent: no name hard-link! dropping the event. (event 2 vp == 0xa5db510 (-UNKNOWN-FILE)).
This baffles me. My umask is 0 meaning files I create and attempt to edit as other users are 777, but I cannot save out edits unless I do a wq! in vi. At that point, the owner of the file changes to whomever did the vi.
This isn't just a vi issue as it happens using any editor, but I like to use vi.
Any help is greatly appreciated. Hey, beer is on me!

Hi all,
Thanks for the replies
I've narrowed it down to a Centos client issue.
Everything works fine using other Linux based OS's as clients.
Since we have such a huge investment in Centos, I must figure out a workaround. Apple support wasn't much help as usual however they were very nice.
There usual response is "its unsupported".
If Apple really wants to play in the enterprise of business space, they really need to change there philosophy. I mean telling me that I shouldn't mount home directories via NFS is completely rediculus.
What am I supposed to use then, Samba of AFP? No, I don't think so. No offense to Microsoft but why would I use a Windows based file sharing protocol to mount network shares in a Nix env???

Accessing NFS mounted share in Finder no longer works in 10.5.3+

I have setup an automounted NFS share previously with Leopard against a RHEL 5 server at the office. I had to go through a few loops to punch a hole through the appfirewall to get the share accessible in the Finder.
A few months later when I returned to the office after a consultancy stint and upgrades to 10.5.3 and 10.5.4 the NFS mount no longer works. I have investigated it today and I can't get it to run even with the appfirewall disabled.
I've been doing some troubleshooting, and the interaction between the statd, lockd and perhaps the portmap seem a bit fishy, even with the appfirewall disabled. Both the statd and lockd complains that they can not register; lockd once and statd indefinitely.
Jul 2 15:17:10 ySubmarine com.apple.statd[521]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
Jul 2 15:17:10 ySubmarine com.apple.launchd[1] (com.apple.statd[521]): Exited with exit code: 1
Jul 2 15:17:10 ySubmarine com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
... and rpcinfo -p gets connection refused unless I start portmap using the launchctl utility.
This may be a bit obscure, and I'm not exactly an expert of NFS, so I wonder if someone else stumbled across this, and can point me in the right direction?
Johan

Sorry for my late response, but I have finally got around to some trial and error. I can mount the share using mount_nfs (but need to use sudo), and it shows up as a mounted disk in the Finder. However, when I start to browse a directory on the share that I can write to, I end up with the lockd and statd failures.
$ mount_nfs -o resvport xxxx:/home /Users/yyyy/xxxx-home
mount_nfs: /Users/yyyy/xxxx-home: Permission denied
$ sudo mount_nfs -o resvport xxxx:/home /Users/yyyy/xxxx-home
Jul 7 10:37:34 zzzz com.apple.statd[253]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
Jul 7 10:37:34 zzzz com.apple.launchd[1] (com.apple.statd[253]): Exited with exit code: 1
Jul 7 10:37:34 zzzz com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
Jul 7 10:37:44 zzzz com.apple.statd[254]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
Jul 7 10:37:44 zzzz com.apple.launchd[1] (com.apple.statd[254]): Exited with exit code: 1
Jul 7 10:37:44 zzzz com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
Jul 7 10:37:54 zzzz com.apple.statd[255]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
Jul 7 10:37:54 zzzz com.apple.launchd[1] (com.apple.statd[255]): Exited with exit code: 1
Jul 7 10:37:54 zzzz com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
Jul 7 10:37:58 zzzz loginwindow[25]: 1 server now unresponsive
Jul 7 10:37:59 zzzz KernelEventAgent[26]: tid 00000000 unmounting 1 filesystems
Jul 7 10:38:02 zzzz com.apple.autofsd[40]: automount: /net updated
Jul 7 10:38:02 zzzz com.apple.autofsd[40]: automount: /home updated
Jul 7 10:38:02 zzzz com.apple.autofsd[40]: automount: no unmounts
Jul 7 10:38:02 zzzz loginwindow[25]: No servers unresponsive
... and firewall wide open.
I guess that the Finder somehow triggers file locking over NFS.

Cannot access external NFS mounts under Snow Leopard

I was previously running Leopard (10.5.x) and automounted an Ubuntu (9.04 Jaunty) Linux NFS mount from my iMac. I had set this up with Directory Utility and it was instantly functional and I never had any issues. After upgrading to Snow Leopard, I set up the same mount point on the same machine (using Disk Utility now), without changing any of the export settings, and Disk Utility stated that the external server had responded and appeared to be working correctly. However, when attempting to access the share, I get a 'Operation not permitted' error. I also cannot manually create the NFS mount using mount or mount_nfs. I get a similar error if I try to cd into /net/<remote-machine>/<share>. I can see the shared folder in /net/<remote-machine>, but I cannot access it (cd, ls, etc). I can see on the Linux machine that the iMac has mounted the share (showmount -a), so the problem appears to be solely in the permissions. But I have not changed any of the permissions on the remote machine, and even then, they are blown wide open (777) so I'm not sure what is causing the issue. I have tried everything as both a regular user, and as root. Any thoughts?
On the Linux NFS server:
% cat /etc/exports
/share 192.168.1.0/24(rw,sync,nosubtree_check,no_rootsquash)
% showmount -a
All mount points on <server>:
192.168.1.100:/share <-- <server> address
192.168.1.101:/share <-- iMac address
On the iMac:
% rpcinfo -t 192.168.1.100 nfs
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
program 100003 version 4 ready and waiting
% mount
trigger on /net/<server>/share (autofs, automounted, nobrowse)
% mount -t nfs 192.168.1.100:/share /Volumes/share1
mount_nfs: /Volumes/share1: Operation not permitted

My guess is that the Linux server is refusing NFS requests coming from a non-reserved (<1024) source port. If that's the case, adding "insecure" to the Linux export options should get it working. (Note: requiring the use of reserved ports doesn't actually make things any more secure on most networks, so the name of the option is a bit misleading.)
If you were previously able to mount that same export from a Mac, you must have been specifying the "-o resvport" option and doing the mounts as root (via sudo or automount which happens to run as root). So that may be another fix.
HTH
--macko

Expdp fails to create .dmp files in NFS mount point in solaris 10,Oracle10g

Dear folks,
I am facing a wierd issue while doing expdp with NFS mount point. Kindly help me on this.
===============
expdp system/manager directory=exp_dumps dumpfile=u2dw.dmp schemas=u2dw
Export: Release 10.2.0.4.0 - 64bit Production on Wednesday, 31 October, 2012 17:06:04
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "/backup_db/dumps/u2dw.dmp"
ORA-27040: file create error, unable to create file
SVR4 Error: 122: Operation not supported on transport endpoint
I have mounted like this:
mount -o hard,rw,noac,rsize=32768,wsize=32768,suid,proto=tcp,vers=3 -F nfs 172.20.2.204:/exthdd /backup_db
NFS=172.20.2.204:/exthdd
given read,write grants to public as well as specific user

782011 wrote:
Hi sb92075,
Thanks for ur reply. pls find the below. I am able to touch the files while exporting log files also creating having the error msg as i showed in previous post.
# su - oracle
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
You have new mail.
oracle 201> touch /backup_db/dumps/u2dw.dmp.test
oracle 202>I contend that Oracle is too dumb to lie & does not mis-report reality
27040, 00000, "file create error, unable to create file"
// *Cause: create system call returned an error, unable to create file
// *Action: verify filename, and permissions

Anyone else having problems with NFS mounts not showing up?

Since Lion, cannot see NFS shares anymore. Folder that had them is still threre but the share will not mount. Worked fine in 10.6.
nfs://192.168.1.234/volume1/video
/Volumes/DiskStation/video
resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276
Any ideas?
Thanks

Since the NFS points show up in the terminal app, go to the local mount directory (i.e. the mount location in the NFS Mounts using Disk Utility) and do the following:
First Create a Link file
sudo ln -s full_local_path link_path_name
sudo ln -s /Volumes/linux/projects/ linuxProjects
Next Create a new directory say in the Root of the Host Drive (i.e. Macintosh HDD)
sudo mkdir new_link_storage_directory
sudo mkdir /Volumes/Macintosh\ HDD/Links
Copy the Above Link file to the new directory
sudo mv link_path_name new_link_storage_directory
sudo mv linuxProjects /Volumes/Macintosh\ HDD/Links/
Then in Finder locate the NEW_LINK_STORAGE_DIRECTORY and then the link file should allow opening of these NFS point points.
Finally, after all links have been created and placed into the NEW..DIRECTORY, Place it into the left sidebar. Now it works just like before.

Accessing NFS mounts in Finder

I currently have trouble accessing NFS mounts with finder. The mount is O.K. I can access the directories on the NFS server in Terminal. However, in Finder when I click on the mount, instead of seeing the contents of the NFS mount I only see the "Alias" icon. Logs show nothing.
I am not sure when it worked the last time. It could well be that the problem only started after one of the lastest snow leopard updates. I know it worked when I upgraded to Snow Leopard.
Any ideas?

Hello gvde,
Two weeks ago I bought a NAS device that touted NFS as one of the features. As I am a fan of Unix boxes I chose an NAS that would support that protocol. I was disappointed to find out that my Macbook would not connect to it. As mentioned in previous posts (by others) on this forum, I could see my NFS share via the command line, but not when using Finder. I was getting pretty upset and racking my brain trying to figure it out. I called the NAS manufacturer which was no help. I used a Ubuntu LiveCD (which connected fine). I was about ready to give up. Then, in another forum someone had mentioned the NFS manager App.
After I installed the app and attempted to configure my NFS shares, the app stated something along the lines of (paraphrasing) "default permissions were incorrect". It then asked me if I would authenticate to have the NFS manager fix the problem. I was at my wits end so I thought why not. Long story short, this app saved me! My shares survive a reboot, Finder is quick and snappy with displaying the network shares, and all is right with the world. Maybe in 10.6.3 Apple will have fixed the default permissions issue. Try the app. It's donationware. I hope this post helps someone else.
http://www.macupdate.com/info.php/id/5984/nfs-manager

WARNING:Expected NFS mount options: rsize =32768,wsize =32768,hard,

While using "dbua" I encountered a problem on the screen saying "cannot open the specified control file" and I was directed to see the new alert log.
The alert log has several lines with messages like:
WARNING:NFS mount of file <PATH>control01.ctl on filesystem <FS_NAME> done with incorrect options
WARNING:Expected NFS mount options: rsize>=32768,wsize>=32768,hard,
WARNING:NFS mount of file <PATH>control02.ctl on filesystem <FS_NAME> done with incorrect options
WARNING:Expected NFS mount options: rsize>=32768,wsize>=32768,hard,
WARNING:NFS mount of file <PATH>/control03.ctl on filesystem <FS_NAME> done with incorrect options
WARNING:Expected NFS mount options: rsize>=32768,wsize>=32768,hard,
ORA-00210: cannot open the specified control file
ORA-00202: control file: '<PATH>/control03.ctl'
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
The file system is actually mounted with these options: "nfs - yes rsize=4096,wsize=4096,hard,intr,vers-3".
Would someone please help to identify what is wrong ?
Thanks

Thanks for your reply.
OS is Solaris on x86-64. and we use NetApps and NFS.
I followed the instruction specified in Oracle Support DocID 781349.1 and as it turned out the order is significant.
The document specifies these mount options using this order.
rw,bg,rsize=32768,wsize=32768,hard,vers=3,nointr,timeo=600,proto=tcp,suid 0 0
** This fixed the problem
FYI, we had these options (and order):
rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,proto=tcp,suid

How to umount a busy NFS mount in solaris 2.6?

How can I umount a busy NFS mount in solaris 2.6 without rebooting the machine? I've tried to check what processes that might hold the mount with the command 'fuser -c /home/user' but it reports nothing.
I wish I had solaris 8 so I could use 'umount -f'...
Can anyone help me?

If your nfs mount is under autofs' control, you would run into issue. Give this a try.
# /etc/init.d/autofs stop
# fuser -ck /home/user
# umount /home/user

Strange delete behavior in Solaris 10 with NFS mounts

We are using the apache commons-io framework to delete a directory in a Solaris 10 environment. The code works well on our dev and qa boxes, but when we load it into our production envrionment we get intermittent failures where the files in a directory are not being deleted and therefore when we try to delete the directory it fails to delete.
We suspect that this may be some kind of NFS problem in Solaris where it may take longer to delete a file than if it is on a local drive and therefore the code reaches the deletedir before the OS actually removes the files and this cause the delete directory failure because files are still present.
Has anyone seen this in an NFS environment with Solaris? We are on Java 1.4.2_15 and we are using apache commons-io 1.3.1.

The apache commons-io framework contains a method to delete a directory by recursively deleting all files and subdirectories. Intermittently, we are seeing some of the files in a subdirectory remain and then when delete is called to remove the directory (from within the commons-io framework deletedir method) we get an IOException. This only occurs on an NFS mounted file system on our production system. Our dev and qa systems are also on an NFS but it is a different one and appears to be loaded differently and the behavior for dev and qa consistently works as expected.
It appears to be some kind of latency issue related to the way java deletes files on the NFS, but no conclusive evidence so far.
We have not tried this with a newer version of java since we are presently constrained to 1.4 :-(

NFS4: Problem mounting NFS mount onto a Solaris 10 Client

Hi,
I am having problems mounting NFS mount point from a Linux-Server onto a Solaris 10 Client.
In the following
=My server IP ..*.120
=Client IP ..*.100
Commands run on Client:
==================
# mount -o vers=3 -F nfs 172.25.30.120:/scratch/pvfs2 /scratch/pvfs2
nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
nfs mount: retrying: /scratch/pvfs2
nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
# mount -o vers=4 -F nfs 172.25.30.120:/scratch/pvfs2 /scratch/pvfs2
nfs mount: 172.25.30.120:/scratch/pvfs2: No such file or directory
# rpcinfo -p
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
1073741824 1 tcp 36084
100024 1 udp 42835 status
100024 1 tcp 36086 status
100133 1 udp 42835
100133 1 tcp 36086
100001 2 udp 42836 rstatd
100001 3 udp 42836 rstatd
100001 4 udp 42836 rstatd
100002 2 tcp 36087 rusersd
100002 3 tcp 36087 rusersd
100002 2 udp 42838 rusersd
100002 3 udp 42838 rusersd
100011 1 udp 42840 rquotad
100021 1 udp 4045 nlockmgr
100021 2 udp 4045 nlockmgr
100021 3 udp 4045 nlockmgr
100021 4 udp 4045 nlockmgr
100021 1 tcp 4045 nlockmgr
100021 2 tcp 4045 nlockmgr
100021 3 tcp 4045 nlockmgr
100021 4 tcp 4045 nlockmgr
# showmount -e 172.25.30.120 (Server)
showmount: 172.25.30.120: RPC: Rpcbind failure - RPC: Unable to receive
Commands OnServer:
================
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 tcp 49927 nlockmgr
100021 3 tcp 49927 nlockmgr
100021 4 tcp 49927 nlockmgr
100021 1 udp 32772 nlockmgr
100021 3 udp 32772 nlockmgr
100021 4 udp 32772 nlockmgr
100011 1 udp 796 rquotad
100011 2 udp 796 rquotad
100011 1 tcp 799 rquotad
100011 2 tcp 799 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 809 mountd
100005 1 tcp 812 mountd
100005 2 udp 809 mountd
100005 2 tcp 812 mountd
100005 3 udp 809 mountd
100005 3 tcp 812 mountd
100024 1 udp 854 status
100024 1 tcp 857 status
# showmount -e 172.25.30.120
Export list for 172.25.30.120:
/scratch/nfs 172.25.30.100,172.25.24.0/4
/scratch/pvfs2 172.25.30.100,172.25.24.0/4
Thank you, ~al

I also tried to run Snoop on the client and wireshark on Server and following is what I see:
One Server: Upon issuing mount command on client:
# tshark -i eth1
Running as user "root" and group "root". This could be dangerous.
Capturing on eth1
0.000000 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
0.205570 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(100005) V:3 UDP
0.205586 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
0.207863 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(100005) V:3 UDP
0.207869 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
2.005314 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
4.011005 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
5.206109 Dell_70:ad:29 -> SunMicro_70:ff:17 ARP Who has 172.25.30.100? Tell 172.25.30.120
5.206277 SunMicro_70:ff:17 -> Dell_70:ad:29 ARP 172.25.30.100 is at 00:14:4f:70:ff:17
5.216157 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(100005) V:3 UDP
5.216170 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
On Clinet Upon issuing mount command on client:
# snoop -d bge1
Using device /dev/bge1 (promiscuous mode)
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=100005 (MOUNT) vers=3 proto=UDP
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 unreachable)
atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=100005 (MOUNT) vers=3 proto=UDP
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 unreachable)
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
pvfs2-io-0-3 -> * ARP C Who is 172.25.30.100, atlas-pvfs2 ?
atlas-pvfs2 -> pvfs2-io-0-3 ARP R 172.25.30.100, atlas-pvfs2 is 0:14:4f:70:ff:17
atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=100005 (MOUNT) vers=3 proto=UDP
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 unreachable)
Also I see the following on Client:
# rpcinfo -p pvfs2-io-0-3
rpcinfo: can't contact portmapper: RPC: Rpcbind failure - RPC: Failed (unspecified error)
When I try the above rpcinfo command on Client and Server Snoop And wireshark(ethereal) outputs are as follows:
Client # snoop -d bge1
Using device /dev/bge1 (promiscuous mode)
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
atlas-pvfs2 -> pvfs2-io-0-3 TCP D=111 S=872 Syn Seq=2065245538 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK>
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (TCP port 111 unreachable)
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=2004 (Unknown), size = 48 bytes
? -> (multicast) ETHER Type=0003 (LLC/802.3), size = 90 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
pvfs2-io-0-3 -> * ARP C Who is 172.25.30.100, atlas-pvfs2 ?
atlas-pvfs2 -> pvfs2-io-0-3 ARP R 172.25.30.100, atlas-pvfs2 is 0:14:4f:70:ff:17
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
atlas-pvfs2 -> pvfs2-io-0-3 TCP D=111 S=874 Syn Seq=2068043912 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK>
pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (TCP port 111 unreachable)
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
Server # tshark -i eth1
Running as user "root" and group "root". This could be dangerous.
Capturing on eth1
0.000000 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
0.313739 Cisco_3d:68:10 -> CDP/VTP/DTP/PAgP/UDLD CDP Device ID: MILEVA Port ID: GigabitEthernet1/0/16
2.006422 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
3.483733 172.25.30.100 -> 172.25.30.120 TCP 865 > sunrpc [SYN] Seq=0 Win=49640 Len=0 MSS=1460 WS=0
3.483752 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
4.009741 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
6.014524 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
6.551356 Cisco_3d:68:10 -> Cisco_3d:68:10 LOOP Reply
8.019386 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
8.484344 Dell_70:ad:29 -> SunMicro_70:ff:17 ARP Who has 172.25.30.100? Tell 172.25.30.120
8.484569 SunMicro_70:ff:17 -> Dell_70:ad:29 ARP 172.25.30.100 is at 00:14:4f:70:ff:17
10.024411 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
12.030956 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
12.901333 Cisco_3d:68:10 -> CDP/VTP/DTP/PAgP/UDLD DTP Dynamic Trunking Protocol
12.901421 Cisco_3d:68:10 -> CDP/VTP/DTP/PAgP/UDLD DTP Dynamic Trunking Protocol
^[[A 14.034193 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
15.691119 172.25.30.100 -> 172.25.30.120 TCP 866 > sunrpc [SYN] Seq=0 Win=49640 Len=0 MSS=1460 WS=0
15.691138 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
16.038944 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
16.550760 Cisco_3d:68:10 -> Cisco_3d:68:10 LOOP Reply
18.043886 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
20.050243 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
21.487689 172.25.30.100 -> 172.25.30.120 TCP 867 > sunrpc [SYN] Seq=0 Win=49640 Len=0 MSS=1460 WS=0
21.487700 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
22.053784 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
24.058680 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
26.063406 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
26.558307 Cisco_3d:68:10 -> Cisco_3d:68:10 LOOP Reply
~thank you for any help you can provide!!!

Cannot write to NFS mount with finder

hi folks
i have moved from a G4 cube running 10.4.9 to a new iMac running os x 10.5.7 (including upgrading from the old machine)
the NFS mounts i used to have with my G4 cube are not working properly; new mounts i've created aren't working properly either.
i can read/open file OK, but when i try to drag & drop files onto the NFS mount using the finder i get errors:
"You may need to enter the name and password for an administrator on this computer to change the item named test.jpg" [ stop ] [ continue ]
clicking "continue" i get:
"The item test.jpg contains one or more items you do not have permission to read. Do you want to copy the items you are allowed to read? [ stop ] [ continue ]
Choosing continue again results in the file appearing in the NFS directory, but with 0 size, and a time stamp of 1970.
if i try to copy the same file using the Terminal, it works fine - so it is not a simple NFS permissions problem - it is something particular to the Finder.
i am able to create a folder inside the NFS director by using the Finder.
i thought at first it might be related to the .DS_Store and similar files being written, so i tried turning off that behaviour:
defaults write com.apple.desktopservices DSDontWriteNetworkStores true
but that hasn't fixed the problem
there are no obvious messages in any of the logs
any suggestions or pointers on how to fix this?

thanks for the reply
these articles appear to relate to sharing a mac filesystem via NFS: exporting the data.
i am referring to mounting a NFS filesystem from another server onto the mac (leopard) client
the mounting works fine: it's just the finder which isn't behaving. the finder worked in tiger; isn't in leopard.

Static NFS Mounts

Similar Messages

Maybe you are looking for