What is the Oracle Solaris NFS Equivalent To "-fsid=num"?
(Doc ID 2008296.1)
Last updated on OCTOBER 18, 2019
Applies to:Solaris Operating System - Version 8.0 to 11.2 [Release 8.0 to 11.0]
Information in this document applies to any platform.
- Grid 11gR2 on Solaris 11, SRU 184.108.40.206.0, SPARC.
- 3 nodes, 2 sites (1 node on site 2).
- ACFS mountpoints on each node, with product binaries, runtime files, etc.
- Each shared via NFS, using (bound to) the Grid VIPs.
- Site-specific NFS client machines connect to the correct node(s) and mount the shares to be used.
The problem is, every time there is some kind of network disconnect, causing VIP migration, the NFS client machines never resume/reconnect their mounts; they simply stay permanently suspended, and all applications running on the NFS client machines fail/hang.
Looking for a possible solution for this situation, we found this:
Oracle ACFS and NFS
When exporting file systems through NFS on Linux, use the -fsid=num exports option. This option forces the file system identification portion of the file handle used to communicate with NFS clients to be the specified number instead of a number derived from the major and minor number of the block device on which the file system is mounted. You can use any 32-bit number for num, but it must be unique among all the exported file systems. In addition, num must be unique among members of the cluster and must be the same num on each member of the cluster for a given file system. This is needed because Oracle ASM DVM block device major numbers are not guaranteed to be the same across reboots of the same node or across different nodes in the cluster.
- What's the Solaris 11 SPARC NFS equivalent to the "-fsid=num" exports option in Linux?
- Where is this option set OS wise?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document