Stress tests NFS by simulating a user application
doing read and write operations
to an NFS mounted file system.
This tests the network over the UDP protocol
at an application level
by copying a large file across the network
to a remote file system and back again,
Then comparing the contents of the original and copied files.
The file system is unmounted
between the write and read operation
to ensure that all data is flushed to the filesystem.
The test passes if it completes a fixed number of iterations
(default 500)
without any loss of data
or loss of access to the NFS server.
Prerequisites
A filesystem must be set up
on both the master and slave machines
that can be mounted as an NFS filesystem
on the other machine.
These filesystems must be writable.
By default, /mnt is used;
to make the filesystem shared, use the following command:
share /mnt
Media types:
All that support NFS.
Init state:
3
Executing machine(s)
master only
Execution time:
Depends upon the ITERATIONS configuration variable;
each iteration takes about 3 seconds.
Execution time varies considerably
depending on the network traffic,
speed of the machine, speed of the media,
filesystem architecture used, and so forth.
Number of test cases:
1
Number of invokable scenarios:
1
Configuration variables:
The parameters for this test are set
only on the master machine
since the test is not run on the slave machine.
REMOTE_MACHINE
Enter the full domain name of the slave machine
being used for testing.
REMOTE_FS
Mount point of the filesystem on the slave machine
that is shared and can be mounted remotely
on the master machine as an NFS filesystem.
Default value is /tmp.
LOCAL_FS
Mount point of the filesystem on the master machine
that is shared and can be mounted remotely
on the slave machine as an NFS filesystem.
Default value is /tmp.
ITERATIONS
Number of times the test should be executed.
Default is 500.