Effective NFS mount options

My computer is running Mac OS X 10.7.5. I have a question regarding NFS mount options.
The following mount options are defined in /etc/nfs.conf
didymus:~ service$ cat /etc/nfs.conf
nfs.client.mount.options = tcp,rw,nfc,intr,async,rdirplus,rsize=65536,wsize=65536
nfs.client.allow_async=1
If I run the mount command, I see the following:
10.72.6.11:/ on /Volumes/10.72.6.11 (nfs, asynchronous, nodev, nosuid, mounted by service)
How do I verify the other mount options specified, intr, rsize, wsize, etc. have taken affect? I presume there is some mechanism for validating this.

Nevermind, appear to have located it: nfsstat -m appears to do the trick.

Similar Messages

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

Best NFS mount options from Linux to Xsan?

So we are adding Linux clients to our network and I'm looking to learn the best NFS mount options to put in the fstab file. Right now they are set "defaults 0 0" and we are having problems. I assume because they are hard mounting. This is from the /proc/mounts file for one of the clients connecting to the Xsan:
10.X.X.X:/snet /snet nfs rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600, retrans=2,sec=sys,mountaddr=10.X.X.X,mountvers=3,mountport=706,mountproto=udp,ad dr=10.X.X.X 0 0
Xsan 2.2, 2 MDCs running 10.6.4, Promise Array.

So we have finally solved this. It turns out that the defaults work just fine. Our issues were solved by changing which MDC was hosting the export, dividing up the workload a bit, our primary was running out of RAM.
Secondly, I added intr and soft to the NFS options, the smoothed things out further.

Linux RHEL 6 Oracle 11.2.0.3 RAC NFS Mount Options

Hi
Does anyone have any details as to what the mount options should be for the following please.
Oracle RAC 11.2.0.3
RHEL 6.3
NFS being used
I need to determine the mount options for both BINARIES and DATABASE FILES (temp, control, data, redo)
I know there must be a document out there that does not involve making the process as complicated as possible
Thanks FORUM

Hi,
Please check Oracle Support note 359515.1 for detail.
Cheers,
SAM L.

How to make autofs to pick up new NFS mount option?

Hi,
I've added a new mount option to an existing map auto_*. I've tried:
svcadm -v restart svc:/system/filesystem/autofs:default
svcadm -v refresh svc:/system/filesystem/autofs:default
but when checking via "mount," it still shows it's mounted before the service restart/refresh and the newly added option is not shown in the output. /etc/mnttab does not show either.
Also this is within a non-global Solaris zone if it makes a difference.
How do I make sure automount picks up the new mount options right away?
Thanks,
Edited by: ACORCL on Feb 12, 2013 4:52 PM

Yes. I restarted/refresh autofs after making a change to auto_* file (adding "llock" option to an existing mount).
I just ran "automount -v" and its output shows that mount point is remounted. However, "mount" output shows
mount_point on NFS_share list_of_options_here on Tue Feb 12 08:47:32 2013 <== which is still 9 hours ago
From where I cannot find the "llock" mount option I added in auto_* file in the "list_of_options_here" above.
If you have any suggestions, please let me know.
Thanks,

Fstab nfs mount options not used

I mount an nfs4 share from fstab with this;
192.168.1.250:/ /mnt/SERVER_NYTT nfs rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp 0 0
What I get is this;( $ mount:)
192.168.1.250:/ on /mnt/SERVER_NYTT type nfs4 (rw,relatime,vers=4,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.251,minorversion=0,local_lock=none,addr=192.168.1.250)
As you see rsize and wsize isn't correct. Mounting manually with
mount -t nfs4 -o rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp 192.168.0.250:/ /mnt/SERVER_NYTT
does give the correct result. Amongst other things I tested my gigabit network for nice rsize and wsize as shown in the manual command above, but they're not used from fstab it seems. 32768 is the default for nfs4.
I see nothing in the logs and export from the server can't change these options, as far as I understand 'man export'. Nothing in the arch wiki about this either.

Above note does not apply to backup location. Just it should be able to write and read from backup location. I/O speed should be good otherwise it becomes nightmare.
regards
Pravin Takpire

Setting umask on NFS mounts under OS X 10.6

I don't see any up to date information on setting umasks with 10.6. We use NFS SAN storage for several folders, mounted using the new NFS Mounts feature of Disk Utility and the SAN and Mac are playing nicely for UID and GID mapping even using our Active Directory LDAP groups and accounts.
However, it creates everything as 755 (umask 0022, the system default) and I'd like to change that umask to 002 to create 775's instead. Nothing for 10.4 or 10.5 seems to apply here (NSUMask, etc.) and it doesn't appear to be a NFS Mount option, either.
NFSv4 and ACLs are not really a good option for me since it's a multiprotocol SAN environment we want to keep NFSv3 permissions bits for UNIX/Linux/MAC and ACLs for Windows. Any ideas how to set the default umask, or at least a way to set the umask for each mount?

xzi wrote:
Yes, I tried that, it does not appear to work on 10.6 that's my point.
I'm sorry, but I just can't figure out "etc". All I can do is keep asking if you have tried this or that. Have tried both variations of that config file and it didn't work? Have you tried instructions in this document, which seems updated for Snow Leopard?
Have you considered that you may have already tried the correct solution, but simply didn't do it correctly? Have you tried with logging-out and back in? With rebooting?

Mount options

We have a filesystem mounted via NFS on 2 systems, both are automounted. When we run a bdf command de filesystem doesnt appear, but if we try to access to the filesystem we can. We would like to know if theres any recommendation about the mount options for filesystems.

The directory is mounted by autmount when you access that directory.
This is exact automount functionaility.
This is why you cannot see in the output of "df" command when you are not using.
The recommended NFS mount option could be ...
if you use NetApp filer as NFS server,
this techinical white paper could be helpful.
http://www.netapp.com/us/library/technical-reports/tr_3442.html
-<snip>-
Correct NFS mount options are important to provide optimal performance and system stability.
Linux®: rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,vers=3,suid,timeo=600
Solaris: rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,vers=3,suid,[forcdirectio or llock]
AIX, HP/UX rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,vers=3,suid

Remove nosuid option from nfs mounts on Mac Os X mountain lion

Hi there
I need to use sticky bit within an NFS export, and to use noowners mount option when I access NFS export from my mac.
So I have mounted the NFS export on my mac and performed a "chmod -R 7777 . " on the root directory of NFS export
I have modified the /etc/nfs.conf file as follows below:
Alessandros-MacBook-Pro:~ alessandro$ cat /etc/nfs.conf
# nfs.conf: the NFS configuration file
nfs.client.mount.options=nodev,noowners
when i mount the export using finder I can see the entry of my NFS export mounted with "noowners" option but also with "nosuid"
that prevents my export to follow sticky bit behaviour.
Alessandros-MacBook-Pro:~ root# mount
/dev/disk0s2 on / (hfs, local, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk1s2 on /Volumes/unit (hfs, local, journaled)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
10.100.10.162:/test_nfs on /Volumes/test_nfs (nfs, nodev, nosuid, noowners, mounted by alessandro)
What could I do in order to do this action by finder preventing the nosuid option to be applied?
Best regards
Alex

I just found the anwer to my own issue. The installation failed on Jam Pack Content 3 disk. To finish the installation I need to go to the Logic Pro Main menu under the item Download supplemental content

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

QFS mount options not getting noticed.

Hi I have a small issue it seems that none of my QFS directives are getting noticed im not sure if this is true or not but this is what I have tried and i am unable to verify that these mount options are actually taking effect..
This is QFS Version 4 revision 4.0.26FA
in my /etc/opt/SUNWsamfs/samfs.cmd I have the following options
fs = qfs1
nosuid
sync_meta = 0
qwrite
readahead = 4096
writebehind = 1024
after mounting my file system why are these options not listed in mnttab
qfs1 /qfs1 samfs dev=1d80036 1048280993
using dd/time to write data to this file system im getting the exact same performance no matter what options I set. another reason why I think these options are being ignored is the following
if I set for example fs = qfs1 and high = 70 low = 30 when I check samu [m] option I dont see those values reflected in the m output so what im asking is there anyway to verifty that my mount options are being set occordinly ?
Yes I did use mount -o nosuid,qwrite,etc.. /qfs1 still no difference and even placing the options in vfstab seems to not make any difference.
last but not lease if i do a samtrace -V while mounting my /qfs1 filesystem I see the following
00100000 readahead (1048576) <<--- still seems to use the default values 1024
00080000 writebehind (524288) <<-- 512 look @ my samfs.cmd file this should but not the value.
Any assistance would be nice.

Hi There! Sorry, it took so long to get back to you. This should help:
The samu N display shows all the mount options. You can also use the samfsinfo command to see file system build information. If the samfs.cmd options are not being picked up, make sure the file is formatted correctly (no odd characters) and is in the proper location, /etc/opt/SUNWsamfs/samfs.cmd . Then "pkill -HUP sam-fsd" to assure the daemon has picked up the file's contents, and then mount the file system.

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

Oracle VM Server 2.2.1 - Extra mount options for /OVS

Hi,
we would like to know how to add extra mount options (rw,hard,intr,tcp,rsize=32768,wsize=32768,timeo=600) to /OVS in Oracle VM 2.2.1.
In version 2.1.5 and lower it was possible by adding those options together with the UUID in /etc/ovs/repositories.options
How to manage mount options in Oracle VM 2.2.1? I've tried the same and no success.
Best regards and thanks in advance,
Marc Caubet

Marc Caubet wrote:
Since we have seen some I/O problems which causes high CPU Wait for some VM (those which contain postgres databases with high I/O activity) we finally decided to apply those NFS options to see if it solves the problem. If it doesn't work we will analize which options can improve the performance.Marc, why not just use the OVS' NFS mount for the system/root partition and mount an NFS volume from within the guest itself? That way, you can set all the parameters you need. Also, the netfront drivers (I'm told) are slightly more efficient that the blockfront drivers, so you could even see a performance improvement.

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!!!

Unable to do expdp on NFS mount point in solaris Oracle db 10g

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=u2dwExport: 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

Hi Peter,
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>

Effective NFS mount options

Similar Messages

Maybe you are looking for