Avoid Poor System Performance

Most systems run administrator scripts to rebuild namespace databases and/or to remove certain files. Unfortunately, running these scripts can degrade StorNext performance. It is recommended that you review administrator scripts to determine if they may adversely affect your StorNext installation and its performance.

For example, many UNIX systems have a find command in the root crontab that traverses the entire directory hierarchy while searching for old temporary and core files. Typically, the find commands are configured only to run on the local file system. However by default, these commands do not skip StorNext file systems because they are considered to be local, even though the file system manager may be running remotely. StorNext performance can be dramatically degraded when these commands visit a StorNext file system if the system contains a large number of files.

If StorNext performance is degraded to an unacceptable level due to the operation of administrator scripts, you can modify them to skip StorNext file systems. A sample command (original and modified is shown below:

On IRIX, by default, the root crontab contains the following find command:

find / -local -type f '(' -name core -o -name dead.letter ')' -atime +7 -mtime + 7 -exec rm -f '{}' ';'

To prevent the find command from searching in StorNext file systems, modify it as shown:

'(' -type d -fstype cvfs -prune ')' -o

The modified find command looks like this:

find / -local '(' -type d -fstype cvfs ')' -o -type f '(' -name core -o -name dead.letter ')' -atime +7 –mtime +7 -exec rm -f '{}' ';'