test

Sun HPC ClusterTools 3.0 Administrator's Guide: With CRE

PFSFileSystem Section

The PFSFileSystem section describes the parallel file systems that Sun MPI applications can use. This description includes

A separate PFSFileSystem section is needed for each parallel file system that you want to create. Example 7-5 shows a sample PFSFileSystem section with two parallel file systems, pfs0 and pfs1.

Example 7-5 PFSFileSystem Section Example


Begin PFSFileSystem=pfs-demo0
NODE            DEVICE              THREADS 
hpc-node0       /dev/rdsk/c0t1d0s2  1
hpc-node1       /dev/rdsk/c0t1d0s2  1 
hpc-node2       /dev/rdsk/c0t1d0s2  1 
End PFSFileSystem

Begin PFSFileSystem=pfs-demo1
NODE            DEVICE              THREADS 
hpc-node3       /dev/rdsk/c0t1d0s2  1
hpc-node4       /dev/rdsk/c0t1d0s2  1 
End PFSFileSystem

Parallel File System Name

The first line shows the name of the parallel file system. PFS file system names must not include spaces.

Server Node Hostnames

The NODE column lists the hostnames of the nodes that function as I/O servers for the parallel file system being defined. The example configuration in Example 7-5 shows two parallel file systems:

Note that I/O server node2 is used by both pfs0 and pfs1. Note also that hostname node3 represents a node that is used as both a PFS I/O server and as a computation server--that is, it is also used for executing application code.

Storage Device Names

The second column gives the device name associated with each member node. This name follows Solaris device naming conventions.

Thread Limits

The THREADS column allows the administrator to specify how many threads a PFS I/O daemon will spawn for the disk storage device or devices it controls. The number of threads needed by a given PFS I/O server node will depend primarily on the performance capabilities of its disk subsystem.