fsx(8) — Maintenance
Digital
NAME
fsx − file system exerciser
SYNOPSIS
/usr/field/fsx [ −h ] [ −ofile ] [ −tn ] [ −fpath ] [ −pm ]
DESCRIPTION
The fsx exerciser exercises a file system by spawning up to 250 (the default is 20) processes that create, open, write, close, open, read, validate, close, and unlink a test file. These test files are created in the /usr/field directory (the default) unless the −fpath option is used. The exerciser will run until a <CTRL-C> or kill −15 pid command is sent to the process.
A logfile is created in /usr/field for you to examine and then remove. If there are errors in the logfile, make sure you check the syslog file where the driver and kernel error messages are saved.
FLAGS
The fsx options are:
−hPrints the help messages for the fsx command.
−ofileSaves the output diagnostics in file.
−tnRun time in minutes (n). The default is to run until the process receives a <CTRL-C> or a kill −15 pid command.
−pmNumber (m) of fsx processes to spawn. The maximum is 250; the default is 20.
−fpath
Path name of directory on file system you wish to test. For example, /mnt or /usr. The default is /usr/field.
EXAMPLES
The following example runs 10 fsx processes on /mnt until the process receives a <CTRL-C> or kill −15 pid command:
% /usr/field/fsx −p10 −f/mnt
The following example runs 20 fsx processes on /usr/field for 120 minutes in the background:
% /usr/field/fsx −t120 &
RESTRICTIONS
If you must run a system exerciser over an NFS link or on a diskless system, there are some restrictions. For exercisers such as fsx(8), which must write into a file system, the target file system must be writable by root. Also, the directory in which any of the exercisers are executed must be writable by root because temporary files are written into the current directory. These latter restrictions are sometimes difficult to overcome because often NFS file systems are mounted in a way that prevents root from writing into them. Some of the restrictions may be overcome by copying the exerciser to another directory and then executing it. Avoid using the fsx exerciser over an NFS or diskless file system.