Home > Storage > PowerScale (Isilon) > Product Documentation > Protocols > PowerScale OneFS NFS Design Considerations and Best Practices > Create NFS export
OneFS supports NFSv3, NFSv4.0, NFSv4.1 and NFSv4.2. OneFS does not implement NFSv4.2 new features, but it allows clients to mount NFS export with NFSv4.2. By default, OneFS has NFS service disabled. You need to enable NFS service first from WebUI or using isi command. Enabling NFSv4.x is non-disruptive on a OneFS cluster, and it will run concurrently with NFSv3. Any existing NFSv3 clients will not be affected by enabling NFSv4.x.
OneFS NFS export is zone-aware, every NFS export is associated with an Access Zone. By default, an access zone named “System” is used if you do not specify an Access Zone name when the export is created. More details about access zones are provided in 3.3 Access zone.
By default, the NFS service applies a root-squashing rule (map the root user to nobody user) for the NFS export. This prevents the client from gaining root privileges to the server despite the user’s credential. Keeping the rule as the default setting is recommended because the root account is the super user in Linux and UNIX environments.
Note: If you are creating an NFSv4.x export, you need to configure a same NFSv4.x domain on both the OneFS cluster and NFSv4.x clients. You can configure the NFSv4.x domain for the OneFS from WebUI or using isi command isi nfs settings zone modify. To configure the NFSv4.x domain for NFSv4.x client, you can edit the Domain = example.local to your NFSv4.x domain in the /etc/idmapd.conf file on the client.