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

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.

  • 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.

  • 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.

  • 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,

  • Some font options not using default system language in font menus

    Font options for Helvetica and Helvetica Neue (e.g. bold, italic, light, etc.) do not use the default system language (English) in the system wide font panel, or in font options within individual applications. Any suggestions as to how to correct this?

    Roderick Ackermann1 wrote:
    Font options for Helvetica and Helvetica Neue (e.g. bold, italic, light, etc.) do not use the default system language (English) in the system wide font panel, or in font options within individual applications. Any suggestions as to how to correct this?
    Could you provide a screen shot of what you are seeing, either here or by email (tom at bluesky dot org)?

  • NFS mount does not work: "Program version wrong"

    I am trying to connect to my Ubuntu Server (8.04) with an NFS share. With OS X 10.6 everything worked fine, using Lion I get the following error in the log file:
    04.10.11 17:45:50,295 com.apple.netauth.user.auth: mount_nfs: can't mount /home/poldi from pc-poldi onto /Volumes/poldi: Program version wrong
    Seems like the NFS client on Lion and the Ubuntu server are not compatible anymore. Anyone knows a solution? A server side upgrade of 'nfs-common' and 'nfs-user-server' did not help.
    Thanks.

    Hey folks, I had this problem and used the nfsvers=2 workaround to fix it, which worked. I wasn't satisfied however, because NFS version 2 isn't as capable in a number of ways as NFS version 3.
    What I learned is that in Snow Leopard, if a mount attempt with NFS version 3 fails, the NFS client will fall back by default to NFS version 2. In Mountain Lion (and possibly Lion, not sure), this fallback doesn't happen and you simply get an error instead. So if you're seeing this after an OS X upgrade from 10.6, then you should not assume that it is a problem on the OS X side (as I did), it may be a problem with the NFSv3 support from the servers you're accessing.
    Linux Details
    In my case, the root cause was a partially failed upgrade of my Linux server from Ubuntu 10.04 to 12.04. The NFS server was only partially working. If I restarted nfs-kernel-service, I saw the following in the messages log:
    Dec 16 21:11:07 myth kernel: [   28.495314] svc: failed to register lockdv1 RPC service (errno 97).
    Dec 16 21:11:07 myth kernel: [   28.496034] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
    Dec 16 21:11:07 myth kernel: [   28.528396] NFSD: starting 90-second grace period
    Also, if you ran "rpcinfo -p" against the server, it was clear that the only versions advertised by mountd were 1 and 2, although the nfs and nlockmgr services were advertising version 3.
    The solution in my case was to re-run the package installers for nfs-kernel-service and nfs-common. Once I did this and restarted the nfs kernel service, I was back to serving NFSv3 from my Linux box, and the original mounts (without the nfsvers=2 qualifier) that had been working under Snow Leopard were working just fine under Mountain Lion.

  • 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 doesn’t appear, but if we try to access to the filesystem we can. We would like to know if there’s 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

  • NFS Mount and WRT160NL

    I'd like to ask a qustion :
    Is it possible add NFS mount to WRT160NL?
    If its possible. i request of the WRT160NL support team add NFS option to storage setup in future firmware.
    Message Edited by cygol on 11-12-2009 12:30 AM

    No,the NFS Mount is not possible in WRT160NL.

  • New files and folders on a Linux client mounting a Windows 2012 Server for NFS share do not inherit Owner and Group when SetGID bit set

    Problem statement
    When I mount a Windows NFS service file share using UUUA and set the Owner and Group, and set the SetGID bit on the parent folder in a hierarchy. New Files and folders inside and underneath the parent folder do not inherit the Owner and Group permissions
    of the parent.
    I am given to understand from this Microsoft KnowledgeBase article (http://support.microsoft.com/kb/951716/en-gb) the problem is due to the Windows implmentation of NFS Services not supporting the Solaris SystemV or BSD grpid "Semantics"
    However the article says the same functionality can acheived by using ACE Inheritance in conjunction with changing the Registry setting for "KeepInheritance" to enable Inheritance propagation of the Permissions by the Windows NFS Services.
    1. The Precise location of the "KeepInheritance" DWORD key appears to have "moved" in  Windows Server 2012 from a Services path to a Software path, is this documented somewhere? And after enabling it, (or creating it in the previous
    location) the feature seems non-functional. Is there a method to file a Bug with Microsoft for this Feature?
    2. All of the references on demonstrating how to set an ACE to achieve the same result "currently" either lead to broken links on Microsoft technical websites, or are not explicit they are vague or circumreferential. There are no plain Examples.
    Can an Example be provided?
    3. Is UUUA compatible with the method of setting ACE to acheive this result, or must the Linux client mount be "Mapped" using an Authentication source. And could that be with the new Flat File passwd and group files in c:\windows\system32\drivers\etc
    and is there an Example available.
    Scenario:
    Windows Server 2012 Standard
    File Server (Role)
    +- Server for NFS (Role) << -- installed
    General --
    Folder path: F:\Shares\raid-6-array
    Remote path: fs4:/raid-6-array
    Protocol: NFS
    Authentication --
    No server authentication
    +- No server authentication (AUTH_SYS)
    ++- Enable unmapped user access
    +++- Allow unmapped user access by UID/GID
    Share Permissions --
    Name: linux_nfs_client.host.edu
    Permissions: Read/Write
    Root Access: Allowed
    Encoding: ANSI
    NTFS Permissions --
    Type: Allow
    Principal: BUILTIN\Administrators
    Access: Full Control
    Applies to: This folder only
    Type: Allow
    Principal: NT AUTHORITY\SYSTEM
    Access: Full Control
    Applies to: This folder only
    -- John Willis, Facebook: John-Willis, Skype: john.willis7416

    I'm making some "major" progress on this problem.
    1. Apparently the "semantics" issue to honor SGID or grpid in NFS on the server side or the client side has been debated for some time. It also existed as of 2009 between Solaris nfs server and Linux nfs clients. The Linux community defaulted to declaring
    it a "Server" side issue to avoid "Race" conditions between simultaneous access users and the local file system daemons. The client would have to "check" for the SGID and reformulate its CREATE request to specify the Secondary group it would have to "notice"
    by which time it could have changed on the server. SUN declined to fix it.. even though there were reports it did not behave the same between nfs3 vs nfs4 daemons.. which might be because nfs4 servers have local ACL or ACE entries to process.. and a new local/nfs
    "inheritance" scheme to worry about honoring.. that could place it in conflict with remote access.. and push the responsibility "outwards" to the nfs client.. introducing a race condition, necessitating "locking" semantics.
    This article covers that discovery and no resolution - http://thr3ads.net/zfs-discuss/2009/10/569334-CR6894234-improved-sgid-directory-compatibility-with-non-Solaris-NFS-clients
    2. A much Older Microsoft Knowledge Based article had explicit examples of using Windows ACEs and Inheritance to "mitigate" the issue.. basically the nfs client "cannot" update an ACE to make it "Inheritable" [-but-] a Windows side Admin or Windows User
    [-can-] update or promote an existing ACE to "Inheritable"
    Here are the pertinent statements -
    "In Windows Services for UNIX 2.3, you can use the KeepInheritance registry value to set inheritable ACEs and to make sure that these ACEs apply to newly created files and folders on NFS shares."
    "Note About the Permissions That Are Set by NFS Clients
    The KeepInheritance option only applies ACEs that have inheritance enabled. Any permissions that are set by an NFS client will
    only apply to that file or folder, so the resulting ACEs created by an NFS client will
    not have inheritance set."
    "So
    If you want a folder's permissions to be inherited to new subfolders and files, you must set its permissions from the Windows NFS server because the permissions that are set by NFS clients only apply to the folder itself."
    http://support.microsoft.com/default.aspx?scid=kb;en-us;321049
    3. I have set up a Windows 2008r2 NFS server and mounted it with a Redhat Enteprise Linux 5 release 10 x86_64 server [Oct 31, 2013] and so far this does appear to be the case.
    4. In order to mount and then switch user to a non-root user to create subdirectories and files, I had to mount the NFS share (after enabling Anonymous AUTH_SYS mapping) this is not a good thing, but it was because I have been using UUUA - Unmapped Unix
    User Access Mapping, which makes no attempt to "map" a Unix UID/GID set by the NFS client to a Windows User account.
    To verify the Inheritance of additional ACEs on new subdirectories and files created by a non-root Unix user, on the Windows NFS server I used the right click properties, security tab context menu, then Advanced to list all the ACEs and looked at the far
    Column reflecting if it applied to [This folder only, or This folder and Subdirectories, or This folder and subdirectories and files]
    5. All new Subdirectories and files createdby the non-root user had a [Non-Inheritance] ACE created for them.
    6. I turned a [Non-Inheritance] ACE into an [Inheritance] ACE by selecting it then clicking [Edit] and using the Drop down to select [This folder, subdirs and files] then I went back to the NFS client and created more subdirs and files. Then back to the
    Windows NFS server and checked the new subdirs and folders and they did Inherit the Windows NFS server ACE! - However the UID/GID of the subdirs and folders remained unchanged, they did not reflect the new "Effective" ownership or group membership.
    7. I "believe" because I was using UUUA and working "behind" the UID/GID presentation layer for the NFS client, it did not update that presentation layer. It might do that "if" I were using a Mapping mechanism and mapped UID/GID to Windows User SIDs and
    Group SIDs. Windows 2008r2 no longer has a "simple" Mapping server, it does not accept flat text files and requires a Schema extension to Active Directory just to MAP a windows account to a UID/GID.. a lot of overhead. Windows Server 2012 accepts flat text
    files like /etc/passwd and /etc/group to perform this function and is next on my list of things to see if that will update the UID/GID based on the Windows ACE entries. Since the Local ACE take precedence "over" Inherited ACEs there could be a problem. The
    Inheritance appears to be intended [only] to retain Administrative rights over user created subdirs and files by adding an additional ACE at the time of creation.
    8. I did verify from the NFS client side in Linux that "Even though" the UID/GID seem to reflect the local non-root user should not have the ability to traverse or create new files, the "phantom" NFS Server ACEs are in place and do permit the function..
    reconciling the "view" with "reality" appears problematic, unless the User Mapping will update "effective" rights and ownership in the "view"
    -- John Willis, Facebook: John-Willis, Skype: john.willis7416

  • Hardware for RAC using NFS mounts

    Hi,
    At a recent Oracle/NetApp seminar we heard that certain RAC configuration could make use of NFS mounts to access its shared storage, leaving SCSI/Fiber/FC Switches out of the picture.
    We're currently looking for a budget cluster configuration that, ideally, is not limited to 2 nodes. The NFS option looks promising, however, our NAS hardware may not be NetApp.
    Has anybody used this kind of setup? For example, several cheap x86 blade servers mounting shared storage via NFS in a NAS.
    Thanks,
    Ivan.

    NAS is NFS.
    See
    Following NFS storage vendors are supported: EMC, Fujitsu, HP, IBM, NetApp, Pillar Data, Sun, Hitachi. 
    NFS file servers do not require RAC certification. The NFS file server must be supported by the system and storage vendors. 
    Currently, only NFS protocol version 3 (NFSv3) is supported.
    Hemant K Chitale

  • 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.

Maybe you are looking for