| Skip Navigation Links | |
| Exit Print View | |
|
Sun QFS File System 5.3 Configuration and Administration Guide Sun QFS and Sun Storage Archive Manager 5.3 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Sun QFS File System 5.3 Configuration and Administration Guide Sun QFS and Sun Storage Archive Manager 5.3 Information Library |
2. About the Master Configuration File
4. Configuring the File System
5. Configuring a Shared File System
How to Configure Shared Sun QFS With NFS
Mounting and Unmounting Shared File Systems
How to Mount a Shared File System
How to Unmount a Shared File System
Adding or Removing a Client Host
How to Add a Client Host to a Shared File System
How to Remove a Client Host From a Shared File System
Updating the mcf file in a Shared File System Environment
Creating the Local Hosts Configuration File
Changing the Metadata Server in a Shared File System Environment
How to Change the Metadata Server When the Metadata Server Is Available
How to Change the Metadata Server When the Metadata Server Is Not Available
Changing the Metadata Server in an Archiving Environment
How to Change the Metadata Server in an Archiving Environment
Converting an Unshared File System to a Shared File System
How to Convert an Unshared Metadata Server to a Shared Metadata Server
How to Add a Client to the Metadata Server
Converting a Shared File System to an Unshared File System
How to Remove a Client From a Shared File System
How to Convert a Shared Metadata Server to an Unshared System
Adding Disk Cache to a File System
How to Add Disk Cache to a File System
How to Back Up and Re-Create a File System
6. Administering File System Quotas
7. Advanced File System Topics
9. Configuring WORM-FS File Systems
11. Using QFS File Systems with SANergy (SAN-QFS)
The behavior of the shared file system is that of an interruptible hard connection. Each client tries repeatedly to communicate with the metadata server even if the server is unavailable. If the metadata server is not responding, a user can terminate any pending, blocked I/O transmission by pressing Ctrl-C. If the I/O attempt is interrupted, the client persists until the I/O completes.
The system generates the following messages to describe status conditions:
SAM-FS: Shared server is not responding.
This message is also generated if the client sam-sharefsd daemon is not active or if the server sam-sharefsd daemon is not active. When the server responds, it generates the following message:
SAM-FS: Shared server is responding.
If the file system is not mounted on the metadata server but it is mounted on the client, the system generates the following message:
SAM-FS: Shared server is not mounted.
When the shared file system mounts on the server, it generates the following message:
SAM-FS: Shared server is mounted.
Because the metadata server looks up file names on behalf of all clients, performance can be slow with the default size of the Oracle Solaris directory name lookup cache (DNLC) on the metadata server. To increase performance when clients are frequently opening a large number of files, you might want to double or even triple the size of this cache from its default.
This procedure is documented in the Oracle Solaris Tunable Parameters Reference Manual. The parameter that controls the size of the directory name lookup cache is ncsize.
|