HP StorageWorks Scalable File Share - Manual (Page 43)

5 Using HP SFS Software
This chapter provides information about creating, configuring, and using the file system.
5.1 Creating a Lustre File System
The first required step is to create the Lustre file system configuration. At the low level, this is
achieved through the use of the mkfs.lustre command. However, HP recommends the use
of the lustre_config command as described in section 6.1.2.3 of the Lustre 1.8 Operations
Manual. This command requires that you create a CSV file which contains the configuration
information for your system that defines the file system components on each file system server.
5.1.1 Creating the Lustre Configuration CSV File
See the example CSV file provided in the HP SFS G3.2-0 software /opt/hp/sfs/scripts/
testfs.csv
tarball and modify with your system-specific configuration. The host name as
returned by uname -n is used in column1, but the InfiniBand IPoIB interface name is used in
the NID specifications for the MGS node and failover node.
For 10 GigE interconnect systems, an example CSV file named /opt/hp/sfs/scripts/
testfs10GbE.csv
is provided. Note the difference in the lnet network specification and NID
specifications.
NOTE: The lustre_config program does not allow hyphens in host names or NID names.
The CSV files that define the Lustre file system configuration and iLO information must be in
UNIX (Linux) mode, not DOS mode. The example files provided as part of the HP SFS G3.2-0
software kit are in UNIX mode. These files might get converted to DOS mode if they are
manipulated, for example with Windows Excel. To convert a file from DOS to UNIX mode, use
a command similar to:
# dos2unix -n oldfile newfile
For the lustre_config program to work, passwordless ssh must be functional between file
system server nodes. This should have been done during Installation Phase 2. See
“Configuring
pdsh ” (page 33) .
The provided CSV file and procedure assumes you have used the HP recommended configuration
with the MGS and MDS nodes as a failover pair, and additional pairs of OSS nodes where each
pair has access to a common set of MSA2000 storage devices.
To determine the multipath storage devices seen by each node that are available for use by Lustre
file system components, use the following command:
# ls /dev/mapper/mpath*
/dev/mapper/mpath4 /dev/mapper/mpath5 /dev/mapper/mpath6
/dev/mapper/mpath7
There should be one mpath device for each MSA2000 storage shelf. A properly configured pair
of nodes should see the same mpath devices. Enforce this by making sure that the /var/lib/
multipath/bindings
file is the same for each failover pair of nodes. After the file is copied
from one node to another, the multipath mappings can be removed with the command:
multipath -F
They can be regenerated using the new bindings file with the command:
multipath -v0
Or the node can be rebooted.
These are the devices available to the Lustre configuration CSV file for use by mgs, mdt, and ost.
5.1 Creating a Lustre File System 43