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.

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

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.

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,

Mount options from Directory Utility

Ok, Directory Utility is gone / hidden into System Preferences...
I used to have a couple NFS mounts defined in Directory Utility. Those are no longer mounted after the upgrade and I don't see where I can set them up again. Anyone found a new way yet?

Thanks for the info. That's good to know

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

Can't mount ntfs from linux

Dear Sirs,
I have install linux Redhat5.3 release 2.6.18-128.el5PAE.i am trying to mount some of the drive of windows 7 on my linux system.
Someone can help me with the rpm for the same.

[linux.softpedia.com/get/System/.../ntfs-3g-15028.shtml] linux.softpedia.com/get/System/.../ntfs-3g-15028.shtml
or
[www.tuxera.com/community/ntfs-3g-download|www.tuxera.com/community/ntfs-3g-download] www.tuxera.com/community/ntfs-3g-download|www.tuxera.com/community/ntfs-3g-download
Use ntfs-3g package to mount ntfs drives into linux.
use following command at shell prompt
$ mount -t /dev/sda1 /mnt/drive_win7
Please find your drive such as sda1 or sda2 or anything from fdisk command and press p to print and press q to quit.
Also, if you want to mount every time you login into linux system.
Then you have to change /etc/inittab file.
Google it out. Easy commands out there for newbies like me and you there.
Regards,
Dave.
Edited by: 897450 on Dec 19, 2011 3:15 AM

How can a mount a NFS share exported from OpenBSD?

Hello Apple Discussions:
I've been experimenting with NFS in a mixed OS environment, and have been successful exporting nfs share with tigerserver, and mounting it on both a powerpc linux system, and on a powerpc openBSD system.
Likewise, I can export a NFS share from the linux powerpc box, and mount it on the openBSD box and on the tigerserver, although, the latter required using the options (ro,sync,insecure) in my exports file.
However, when I export a share on the OpenBSD box, I can mount it on the linux box, but not on tigerserver.
I would like for the OpenBSD box to export a NFS share securely, with read-write permissions, to the tigerserver.
After reading so many tutorials, that it would be a page of links, just to list them all, I am pulling my hair out. However, I have found one thread that suggests, that perhaps what I'm trying to do is impossible:
http://www.bsdforums.org/forums/showthread.php?t=54308
Here it is suggested that the NFS won't work because tigerserver is not using UTF-8?
I will have to say, that I was somewhat alarmed, that the only times I succeeded in mounting an nfs share exported from linux onto tigerserver, it was when the "insecure" option is used in the /etc/exports file. There doesn't seem to be an equivalent for the linux style exports option "insecure", in the bsd style options of --maproot=user:group1:group2.
But I don't like using any options that say "insecure" anyways, so rather than trying to find out how to make openbsd "insecure", I would rather like to find out if there is a way to get tigerserver using UTF-8, at least when mounting NFS shares, if this is indeed the issue.
Here are the more technical details. I've created a user on all sytems named "fives" with the userid of 5555 and the groupid of 5555. I made the user local user in the local net info domain, but I've tried it with an LDAP user as well. The folders I wish to export and the folders into which to mount them are all owned by user fives and group fives, and have permissions set to 0775. The ip addresses are OpenBSD=192.168.222.111 TigerServer=192.168.222.233 LinuxPPC=192.168.222.253. I've included the relevant NFS setup files and running processes below:
ON THE OPENBSD BOX:
#/etc/exports
/fives -alldirs -network=192.168.222.0 -mask=255.255.255.0
/exports/fives -mapall=fives:fives 192.168.222.233 192.168.222.253
#/etc/hosts.deny
ALL: ALL
#/etc/hosts.allow
ALL: 192.168.222.233 192.168.222.253
#/etc/rc.conf.local
portmap=YES
lockd=YES
nfs_server=YES
#here's proof that the daemons are running on the OpenBSD box;
rpcinfo -p localhost
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 1 udp 863 mountd
100005 3 udp 863 mountd
100005 1 tcp 613 mountd
100005 3 tcp 613 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100021 1 udp 895 nlockmgr
100021 3 udp 895 nlockmgr
100021 1 tcp 706 nlockmgr
100021 3 tcp 706 nlockmgr
# actually, I don't see statd, but haven't found the equivalent in openbsd. There's rpc.rstatd, and maybe it should be listed here, but there doesn't seem to be a way to launch it directly. This is a competitor with the UTF-8 theory about why it's not working.
ON THE TIGER SERVER:
# here's proof that tiger server sees the mounts:
showmount -e 192.168.222.111
Exports list on 192.168.222.111:
/fives 192.168.222.0
/exports/fives 192.168.222.233 192.168.222.253
# here's the result of user fives' attempt at mounting a share:
sudo mount -t nfs 192.168.222.111:/exports/fives /imports/fives
mount_nfs: /imports/fives: Permission denied
# yet user fives has no problem mounting same share on linuxppc box.
What is different about OSX server? I thought it was supposed to speak NFS?
---argh... I'm steppin out for a pint.. Hopefully when I'm back it'll just work.

One thing not mentioned is that if you decide on the multiple user approach, you can have your music folder in Shared Documents so you only store the tracks once.
Each user is free to choose which of those tracks they want in their library.
There is an Apple help article on multiple users.
http://docs.info.apple.com/article.html?artnum=300432

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

Slow nfs read/write from solaris 8 to solaris 10

there is a bug:4852269 which sums up my problem well.
I have a solaris 10 sparc with a big nfs shared raid5, and most of the other suns I have run solaris 8. the access time from sol8 to sol10 is awfull.
Is there some config/patch I can apply to the solaris 10 box?
I have put on the latest 10_Recommended.zip

it's a ufs filesystem
If it helps, here is my /etc/default/nfs
# ident "@(#)nfs 1.10 04/09/01 SMI"
# Copyright 2004 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# Sets the maximum number of concurrent connection oriented connections.
# Default is unlimited and is obtained by not setting NFSD_MAX_CONNECTIONS.
# Equivalent to -c.
#NFSD_MAX_CONNECTIONS=
# Set connection queue length for the NFS over a connection-oriented
# transport. The default value is 32 entries.
# Equivalent to -l.
NFSD_LISTEN_BACKLOG=32
# Start NFS daemon over the specified protocol only.
# Equivalent to -p, ALL is equivalent to -a on the nfsd command line.
# Mutually exclusive with NFSD_DEVICE.
NFSD_PROTOCOL=ALL
# Start NFS daemon for the transport specified by the given device only.
# Equivalent to -t.
# Mutually exclusive with setting NFSD_PROTOCOL.
#NFSD_DEVICE=
# Maximum number of concurrent NFS requests.
# Equivalent to last numeric argument on nfsd command line.
NFSD_SERVERS=16
# Set connection queue length for lockd over a connection-oriented transport.
# Default and minimum value is 32.
LOCKD_LISTEN_BACKLOG=32
# Maximum number of concurrent lockd requests.
# Default is 20.
LOCKD_SERVERS=20
# Retransmit Timeout before lockd tries again.
# Default is 5.
LOCKD_RETRANSMIT_TIMEOUT=5
# Grace period in seconds that all clients (both NLM & NFSv4) have to
# reclaim locks after a server reboot. Also controls the NFSv4 lease
# interval.
# Overrides the deprecated setting LOCKD_GRACE_PERIOD.
# Default is 90 seconds.
GRACE_PERIOD=90
# Deprecated.
# As for GRACE_PERIOD, above.
# Default is 90 seconds.
#LOCKD_GRACE_PERIOD=90
# Sets the minimum version of the NFS protocol that will be registered
# and offered by the server. The default is 2.
#NFS_SERVER_VERSMIN=2
# Sets the maximum version of the NFS protocol that will be registered
# and offered by the server. The default is 4.
NFS_SERVER_VERSMAX=2
# Sets the minimum version of the NFS protocol that will be used by
# the NFS client. Can be overridden by the "vers=" NFS mount option.
# The default is 2.
#NFS_CLIENT_VERSMIN=2
# Sets the maximum version of the NFS protocol that will be used by
# the NFS client. Can be overridden by the "vers=" NFS mount option.
# If "vers=" is not specified for an NFS mount, this is the version
# that will be attempted first. The default is 4.
#NFS_CLIENT_VERSMAX=4
# Determines if the NFS version 4 delegation feature will be enabled
# for the server. If it is enabled, the server will attempt to
# provide delegations to the NFS version 4 client. The default is on.
#NFS_SERVER_DELEGATION=on
# Specifies to nfsmapid daemon that it is to override its default
# behavior of using the DNS domain, and that it is to use 'domain' as
# the domain to append to outbound attribute strings, and that it is to
# use 'domain' to compare against inbound attribute strings.
#NFSMAPID_DOMAIN=domain
#

IPhoto 09 & storing "Originals" directory in NFS-mounted partitition

In iPhoto 08, I had the Originals directory NFS mounted off a Linux server. On the Mac, I mounted it at /Volumes/pics and I had a symbolic link pointing from iPhoto Library/Originals to /Volumes/pics. Everything was hunky-dory.
I upgraded to iPhoto 09 and now it will not import new pictures. I get the following error message:
iPhoto cannot import your photos to this library because iPhoto cannot access the library.
Anyone have any ideas on how to store the original pictures on an NFS-mounted partition

Ok. I figured this out myself.
I mounted the NFS volume directly on ~/Pictures/iPhoto Library/Originals. This seems to fix the problem.
So, it's not the NFS mounting that's the issue. It's the symbolic link to /Volumes/pics.
Weird.

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

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

Best NFS mount options from Linux to Xsan?

Similar Messages

Maybe you are looking for