Home > Storage > PowerScale (Isilon) > Product Documentation > Protocols > PowerScale OneFS NFS Design Considerations and Best Practices > NFS export considerations
NFS export read size and write size on OneFS
While mounting export to a client, you can specify the read size (rsize) and write size (wsize) options. Larger rsize and wsize improve the throughput performance. By default in OneFS, the rsize of 128 KB and wsize of 512 KB are advertised for NFSv3 Linux clients, but can be set as high as 1 MB. NFSv4.x defaults to 1 MB for both rsize and wsize. Explicitly setting these values too small will override the default value and might result in slower than optimal performance.
NFS aliases
In general, create an export with short path when possible. If the long directory path must be used, you can create an NFS alias for the directory path. An NFS alias is designed to give functional parity with SMB share name within the context of NFS. It provides a shortcut for the path. Like exports, NFS aliases are also access zone-ware. You can specify the access zone when you create an alias. You can check the status of an alias from the WebUI or using isi command isi nfs aliases with --check option (status can be: good, illegal path, name conflict, not exported, or path not found).
NFSv3 encoding support
OneFS 8.1.1.1 includes enhancements to NFSv3 encoding. This sets the cluster encoding and export encoding to the same character set using RFC-compliant filenames, enabling exports to any NFSv3 client that uses western or nonwestern characters.
Before OneFS 8.1.1.1, non-utf-8 encoded files or directories may be inaccessible to NFSv3 and NFSv4.x clients. If this issue occurs in your environment, contact Dell technical support service to help solve the issue or upgrade your OneFS cluster to OneFS 8.1.1.1 or higher.
32-bit file IDs over NFS
The NFS protocol supports 64-bit file IDs from NFSv3 onwards. However, some applications do not support 64-bit file IDs. To accommodate these applications, OneFS allows enabling 32-bit file IDs from WebUI or using isi command isi nfs export <exportID> --return-32bit-file-ids.
Note: When this change is made, all clients must be remounted. Clients that are not remounted will encounter errors such as "error: fileid changed," or the clients will continue to receive 64-bit file IDs. You might need to schedule a maintenance window before making this change.