Quantum 3.5.1 User Manual

Chapter 6  Managing the File System

Managing File System Operations

StorNext User’s Guide

105

subsequent machines listed serve as backup coordinators. To create 

redundancy, it is recommended that you list two machines. Typically, the 

selected systems are also configured for FSM services, but this is not a 

requirement.
If the fsnameservers file does not exist, then the file system operates as a 

local file system, requiring both a client and a server. The file system will 

not communicate with any other StorNext File System product on the 

network, thus eliminating the sharing of the FSS over the SAN.

After you type the IP addresses of two reliable machines on your network 

in the fsnameservers file, copy the fsnameservers file to every machine 

running SNFS. After changing the fsnameservers file, always restart 

(stop and start) all file system services running on the SNFS.
Redundant NICs are supported in the fsnameservers file; simply list both 

NIC addresses in the file.

6

Use the following procedures to make or re-make a file system.

It is extremely important that all copies of /usr/cvfs/config/
fsnameserver

 file in a SAN be identical. A stale 

configuration on a system that is not in use can cause 

election problems if fsmpm processes are running with 

mismatched fsnameservers.

It is also critical to verify that complete network 

connectivity exists between all systems running SNFS 

(client or server). This is important because all StorNext 

systems participate in the failover process.

This task destroys all existing data for the selected file 

system and creates a new configuration. Making or re-

making a file system results in a complete loss of user data.

After remaking a managed file system, you must delete or 

recreate the relation points.