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

Similar Messages

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

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.

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,

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.

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>

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

Mount option

HI,
I have the following task.
remounted with the “-o nolock” option.Mount point Name: /Shareplex_migration
I have unmount the file system , then edit the fstab with "nolock" & mount it again. I did the following steps. is it ok? because he mentioned to mount with "-o nolock" but i mount it with nolock only (edited fstab with nolock).
============================
#umount /Shareplex_migration
vi /etc/fstab
ad2hfdnas016:/vol/HFD_flx_445/Shareplex_migration /Shareplex_migration nfs hard,bg,proto=tcp,suid,rsize=32768,wsize=32768,nolock,noac 0 0
#mount /Shareplex_migration
================================
Regards,
Ani

If you use a mountpoint as the only parameter for the mount command, then the command has to read the details/parameters for that mountpoint from +/etc/fstab+.
PS. see section +"The /etc/fstab, /etc/mtab and /proc/mounts files"+ in the manpage for the mount command.

NFS Mount Hanging During 11g R2 RAC Install on OEL 5.4

Hello, I am trying to create two-node Oracle 11g R2 RAC on OEL 5 Update 4. I am doing so by following the Tim Hall's article at
http://www.oracle-base.com/articles/11g/OracleDB11gR2RACInstallationOnLinuxUsingNFS.php
I have two separate physical machines with OEL 5, and their IP configuration is as follows in /etc/hosts file:
#NAS
192.168.2.101 nas1.localdomain nas1
I have added the following lines to the "/etc/fstab" file.
nas1:/shared_config /u01/shared_config nfs rw,bg,hard,nointr,tcp,vers=3,timeo=600,rsize=32768,wsize=32768,actimeo=0 0 0
nas1:/shared_grid /u01/app/11.2.0/grid nfs rw,bg,hard,nointr,tcp,vers=3,timeo=600,rsize=32768,wsize=32768,actimeo=0 0 0
nas1:/shared_home /u01/app/oracle/product/11.2.0/db_1 nfs rw,bg,hard,nointr,tcp,vers=3,timeo=600,rsize=32768,wsize=32768,actimeo=0 0 0
nas1:/shared_data /u01/oradata nfs rw,bg,hard,nointr,tcp,vers=3,timeo=600,rsize=32768,wsize=32768,actimeo=0 0 0
When I try to mount the NFS share on both servers, it hangs:
mount /u01/shared_config
regards

I am also getting same issue. How did you resolve.?

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?

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

Systemd and nfs .mount

Hi,
I'm trying to setup a systemd unit for my NFS mounts. I don't want to use /etc/fstab because I want an openvpn.service dependency. However, for now, I'm omitting that dependency due to debugging. Here is the current unit file I have:
# cat host\@.mount
[Unit]
Description=%i mount
DefaultDependencies=no
Requires=local-fs.target network.target rpc-statd.service
Conflicts=umount.target
[Mount]
What=host:/%i
Where=/%i
Type=nfs
Options=user,async,atime,exec,rw,wsize=32768,rsize=32768
DirectoryMode=0755
TimeoutSec=20
[Install]
WantedBy=multi-user.target
When I try to enable this I get the famously vague error:
# systemctl enable ./host\@mnt.mount
Failed to issue method call: Invalid argument
Any ideas on how to fix this? Thanks!

The solution is NOT to create this file at all. Apparently, exports from the server do not require them. If I remove it and reboot the server, I am able to connect from my workstation with no issues. For reference:
$ ls -l /etc/systemd/system/multi-user.target.wants/
total 0
lrwxrwxrwx 1 root root 40 May 10 10:58 cpupower.service -> /usr/lib/systemd/system/cpupower.service
lrwxrwxrwx 1 root root 38 May 10 10:58 cronie.service -> /usr/lib/systemd/system/cronie.service
lrwxrwxrwx 1 root root 40 May 10 12:10 exportfs.service -> /usr/lib/systemd/system/exportfs.service
lrwxrwxrwx 1 root root 42 May 10 10:59 lm_sensors.service -> /usr/lib/systemd/system/lm_sensors.service
lrwxrwxrwx 1 root root 35 Apr 30 15:15 network.service -> /etc/systemd/system/network.service
lrwxrwxrwx 1 root root 36 May 10 10:59 ntpd.service -> /usr/lib/systemd/system/ntpd.service
lrwxrwxrwx 1 root root 36 May 10 11:33 rc-local.service -> /etc/systemd/system/rc-local.service
lrwxrwxrwx 1 root root 40 May 2 22:37 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
lrwxrwxrwx 1 root root 39 May 10 10:58 rpcbind.service -> /usr/lib/systemd/system/rpcbind.service
lrwxrwxrwx 1 root root 42 May 10 12:10 rpc-mountd.service -> /usr/lib/systemd/system/rpc-mountd.service
lrwxrwxrwx 1 root root 41 May 10 12:10 rpc-statd.service -> /usr/lib/systemd/system/rpc-statd.service
lrwxrwxrwx 1 root root 43 May 10 10:58 sshdgenkeys.service -> /usr/lib/systemd/system/sshdgenkeys.service
lrwxrwxrwx 1 root root 36 May 10 10:58 sshd.service -> /usr/lib/systemd/system/sshd.service
lrwxrwxrwx 1 root root 41 May 10 11:06 syslog-ng.service -> /usr/lib/systemd/system/syslog-ng.service
lrwxrwxrwx 1 root root 35 May 10 10:57 ufw.service -> /usr/lib/systemd/system/ufw.service

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

Similar Messages

Maybe you are looking for