HP StorageWorks Scalable File Share - Manual (Page 31)

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.6 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.
Refer to the example CSV file provided in the HP SFS G3.0-0 Software tarball /opt/hp/sfs/
scripts/testfs.csv
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.
NOTE: The lustre_config program does not allow hyphens in host names or NID names.
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 25) .
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 be able to 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 coped 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.
To see the multipath configuration, use the following command. Output will be similar to the
example shown below:
# multipath -ll
mpath7 (3600c0ff000d547b5b0c95f4801000000) dm-5 HP,MSA2212fc
[size=4.1T][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=20][active]
\_ 0:0:3:5 sdd 8:48 [active][ready]
\_ 1:0:3:5 sdh 8:112 [active][ready]
mpath6 (3600c0ff000d548aa1cca5f4801000000) dm-4 HP,MSA2212fc
[size=4.1T][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=20][active]
\_ 0:0:2:6 sdc 8:32 [active][ready]
\_ 1:0:2:6 sdg 8:96 [active][ready]
5.1 Creating a Lustre File System 31