5 starting heartbeat, 6 monitoring failover pairs – HP StorageWorks Scalable File Share User Manual

Page 48

Advertising
background image

5.2.5 Starting Heartbeat

IMPORTANT:

You must start the Lustre file system manually in the following order; MGS,

MDT, OST, and verify proper file system behavior on sample clients before attempting to start
the file system using Heartbeat. For more information, see

“Creating a Lustre File System”

(page 41)

.

Use the mount command to mount all the Lustre file system components on their respective
servers, and also to mount the file system on clients. When proper file system behavior has been
verified, unmount the file system manually using the umount command on all the clients and
servers and use Heartbeat to start and stop the file system as explained below and in

“Starting

the File System” (page 49)

.

After all the files are in place, starting Heartbeat with service heartbeat start starts the
Lustre servers by mounting the corresponding file systems. After initial testing, Heartbeat should
be permanently enabled with chkconfig --add heartbeat, or chkconfig heartbeat
on

.

5.2.6 Monitoring Failover Pairs

Use the crm_mon command to monitor resources in a failover pair.

In the following sample crm_mon output, there are two nodes that are Lustre OSSs, and eight
OSTs, four for each node.

============
Last updated: Thu Sep 18 16:00:40 2008
Current DC: n4 (0236b688-3bb7-458a-839b-c19a69d75afa)
2 Nodes configured.
10 Resources configured.
============

Node: n4 (0236b688-3bb7-458a-839b-c19a69d75afa): online
Node: n3 (48610537-c58e-48c5-ae4c-ae44d56527c6): online

Filesystem_1 (heartbeat::ocf:Filesystem): Started n3
Filesystem_2 (heartbeat::ocf:Filesystem): Started n3
Filesystem_3 (heartbeat::ocf:Filesystem): Started n3
Filesystem_4 (heartbeat::ocf:Filesystem): Started n3
Filesystem_5 (heartbeat::ocf:Filesystem): Started n4
Filesystem_6 (heartbeat::ocf:Filesystem): Started n4
Filesystem_7 (heartbeat::ocf:Filesystem): Started n4
Filesystem_8 (heartbeat::ocf:Filesystem): Started n4
Clone Set: clone_9
stonith_9:0 (stonith:external/riloe): Started n4
stonith_9:1 (stonith:external/riloe): Started n3
Clone Set: clone_10
stonith_10:0 (stonith:external/riloe): Started n4
stonith_10:1 (stonith:external/riloe): Started n3

The display updates periodically until you interrupt it and terminate the program.

5.2.7 Moving and Starting Lustre Servers Using Heartbeat

Lustre servers can be moved between nodes in a failover pair, and stopped, or started using the
Heartbeat command crm_resource. The local file systems corresponding to the Lustre servers
appear as file system resources with names of the form Filesystem_n, where n is an integer.
The mapping from file system resource names to Lustre server mount-points is found in cib.xml.
For example, to move Filesystem_7 from its current location to node 11:

# crm_resource -H node11 -M -r Filesystem_7

48

Using HP SFS Software

Advertising