2 configuring heartbeat – HP StorageWorks Scalable File Share User Manual
Page 32
mpath5 (3600c0ff000d5455bc8c95f4801000000) dm-3 HP,MSA2212fc
[size=4.1T][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=50][active]
\_ 1:0:1:5 sdf 8:80 [active][ready]
\_ round-robin 0 [prio=10][enabled]
\_ 0:0:1:5 sdb 8:16 [active][ready]
mpath4 (3600c0ff000d5467634ca5f4801000000) dm-2 HP,MSA2212fc
[size=4.1T][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=50][active]
\_ 0:0:0:6 sda 8:0 [active][ready]
\_ round-robin 0 [prio=10][enabled]
\_ 1:0:0:6 sde 8:64 [active][ready]
After you have completed creating your file system configuration CSV file, proceed using the
following directions:
1.
Run the following on the MGS node n1:
# lustre_config -v -f -w n1 testfs.csv
Examine the script output for errors. If completed successfully, you will see a line added to
the /etc/fstab file with the mount-point information, and the MGS mount-point created
as specified in the CSV file.
2.
To proceed with the remaining steps, mount the MGS mount-point:
# mount /mnt/mgs
3.
Still on the MGS node n1, but for the MDS node n2, and OSS nodes n3 through n6:
# lustre_config -v -f -w n2,n3,n4,n5,n6 testsfs.csv
Examine the script output for errors. If completed successfully, you will see a line added to
the /etc/fstab file with the mount-point information for each node, and the mount-points
created as specified in the CSV file. This creates the file system mdt and ost components on
the other file system server nodes. There are /etc/fstab entries for these, but the noauto
mount
option is used so the file system components do not start up automatically on reboot.
The Heartbeat service is used to actually mount the file system components, as explained
in
“Configuring Heartbeat” (page 32)
. The lustre_config script also modifies /etc/
modprobe.conf
as needed on the file system server nodes. The lustre_config command
can take hours to complete depending on how large the disks are.
4.
Unmount the MGS:
# umount /mnt/mgs
5.2 Configuring Heartbeat
HP SFS G3.0-0 uses Heartbeat V2.1.3 for failover. Heartbeat is open source software. Heartbeat
RPMs are included in the HP SFS G3.0-0 kit. More information and documentation is available
at
.
IMPORTANT:
This section assumes you are familiar with the concepts in the Failover chapter
of the Lustre 1.6 Operations Manual.
HP SFS G3.0-0 uses Heartbeat to place pairs of nodes in failover pairs, or clusters. A Heartbeat
failover pair is responsible for a set of resources. Heartbeat resources are Lustre servers: the MDS,
the MGS, and the OSTs. Lustre servers are implemented as locally-mounted file systems, for
example, /mnt/ost13. Mounting the file system starts the Lustre server. Each node in a failover
pair is responsible for half of the servers and the corresponding mount-points. If one node fails,
the other node in the failover pair mounts the file systems that belonged to the failed node causing
the corresponding Lustre servers to run on that node. When a failed node returns, the
mount-points can be transferred to that node either automatically or manually, depending on
32
Using HP SFS Software