Protocol: NFSv[2-4] Bytes

This statistic shows NFSv[2-4] bytes/second transferred between NFS clients and Oracle ZFS Storage Appliance. Supported NFS versions are: NFSv2, NFSv3, NFSv4.0, and NFSv4.1. Bytes statistics can be broken down by: operation, client, filename, share, and project.

When to Check NFSv[2-4] Bytes

NFSv[2-4] bytes/sec can be used as an indication of NFS load. The best way to improve performance is to eliminate unnecessary work, which can be identified through the client and filename breakdowns, and the filename hierarchy view. Client and especially filename breakdowns can be very expensive in terms of storage and execution overhead. Therefore, it is not recommended to permanently enable these breakdowns on a busy production Oracle ZFS Storage Appliance.

NFSv[2-4] Bytes Breakdowns

Table 5-43 Breakdowns of NFS Bytes

Breakdown Description

type of operation

NFS operation type (read/write/getattr/setattr/lookup/...).


Remote hostname or IP address of the NFS client.


Filename for the NFS I/O, if known, and cached by Oracle ZFS Storage Appliance. There are some circumstances where the filename is not known, such as after a cluster failover, and when clients continue to operate on NFS file handles without issuing an open request to identify the filename; in these situations the filename reported is <unknown>.

Application ID

Identity of the client application issuing the I/O. This breakdown is available only for OISP-enabled NFSv4.0 and NFSv4.1 clients.


The share for this NFS I/O.


The project for this NFS I/O.

These breakdowns can be combined to produce powerful statistics. For example, use Protocol: NFSv3 bytes per second for client broken down by filename to view which files a particular client is accessing.

Further Analysis