NFS Shares Test

Often, if an NFS file system fails, the directories mapped to the NFS file system will be unavailable. Accesses to these directories/files will take a long time and ultimately fail. This could potentially result in application failures and outages. Hence, administrators need the capability to detect when an NFS file system is unavailable or is running out of space. This test provides administrators with this capability.

This test executes on an NFS client, auto-discovers all NFS-mounted directories, and reports in real-time the availability and space usage of each of these directories.

Target of the test : NFS on Linux Client

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every NFS-mounted directory auto-discovered.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.


The host for which the test is to be configured.


Specify the maximum duration (in seconds) for which the test will wait for a response from the server. The default timeout period is 30 seconds.

Exclude File Systems

Provide a comma-separated list of file systems andd/or file system patterns to be excluded from monitoring. A file system pattern can be of the format *expr*, *exp, or expr*. A leading '*' signifies any number of leading characters, while a trailing '*' signifies any number of trailing characters. For instance, your specification can be: shares,*dev*,/User*,*prod. In this case, the following file systems will be excluded from monitoring:

  • File system named shares
  • File systems with names containing the string dev
  • File systems with names that begin with /User
  • File systems with names that end with prod

By default, this parameter is set to none, indicating that all file systems will be monitored by default.

Report by File System

This test reports a set of measures for every NFS-mounted directory auto-discovered on a target NFS client – this implies that  the discovered directory names will appear as descriptors of this test in the eG monitoring console. By selecting an option from the report by file system list, you can indicate how you want to display these directory names in the eG monitoring console. By default, the Remote Filesystem option is chosen; this indicates that, by default, the eG monitoring console will refer to each directory using the complete path to that directory in the remote file system – typically, this would include the name of the remote file system. For instance, if the shares directory on a remote host with IP is being monitored, then the corresponding descriptor will be: //

If you choose the Local Filesystem option instead, then, the eG monitoring console will display only the name of the local file that is mapped to the remote directory – for example, if the // directory is locally mapped to the file /mnt, then the descriptor will be /mnt.

Alternatively, you can have both the remote file system path and the local file mapping displayed in the eG monitoring console, by selecting the Both option from this list. In such a case, the descriptor will be of the format: // (/mnt).

Measurements made by the test
Measurement Description Measurement Unit Interpretation


Indicates whether the directory is accessible or not.


The value 100 indicates that the mounted NFS is accessible.

The value 0  indicates that the mounted NFS is not accessible.

Total capacity

Indicates the current total capacity of the mounted system disk partition.



Used space

Indicates the amount of space currently used in a mounted system disk partition.



Free space

Indicates the free space currently available on a disk partition of a mounted system.



Percent usage

Indicates the percentage of space used on a mounted system disk partition.


Ideally, this value should be low. A high value or a value close to 100% is indicative of excessive space usage on this mounted system disk partition. If a number of NFS directories are exhibiting similar usage patterns, it is a definite cause for concern, as it indicates that the NFS file system as a whole couple be running out of space. If this situation is not brought under control soon, application failures and outages will become inevitable!