
You must keep distribution maintainers documentation for specific mount syntax. We have not provided specific mount strings, as the syntax used to define these options varies depending on the operating system in use. While we do not have hard requirements for mount options, we do make some recommendations on how clients connection. Here is the official release information for 9.3: NFSv4.1 and v4.2 are available starting in OneFS version 9.3 Only supports TCP - Version 4 of NFS has left loss and retransmission up to the underlying operating system.This is used to reduce the number of calls involved in common operations.
#Isilon support series#
Compound Calls - Version 4 can bundle a series of calls in a single packet, allowing the server to process all of them and reply at the end.File Locking is in band - Version 4 no longer users a separate protocol for file locking, instead making it a type of call that is usually compounded with OPENs, CREATES, or WRITES.The server must lookup names to present, while the client must remap those to numbers on it s end. User and Group info is presented as strings - Both the client and server must resolve the names of the numeric information stored.Prior to OneFS 8.X this meant that NFSv4 clients required static IP pools on the PowerScale or could encounter issues.Stateful - NFSv4 uses sessions in order to handle communication, as such both client and server must track session state to continue communicating.Here are some of the key differences between v3 and v4 At this time NFSv4 is generally less performant than v3 against the same workflow due to the greater amount of identity mapping and session tracking work required to reply. NFS version 4 is the newest major revision of the NFS protocol, and is increasing in adoption.
#Isilon support software#
Can run over TCP or UDP - This version of the protocol can run over UDP instead of TCP, leaving handling of loss and retransmission to the software instead of the operating system.This requires the client to respond to RPC messages from the server to confirm locks have been granted, so on File Locking is out of band - Version 3 of NFS uses a helper protocol called NLM to perform locks.User and Group info is presented numerically - Client and Server communicate user information by numeric identifiers, allowing the same user to appear as different names between client and server.This allows for simple failover between OneFS nodes using dynamic IP pools.

