HP StorageWorks Scalable File Share User Manual
Page 55
The problem is in line #08. The MDT is related to 10.129.10.1@o2ib, but in this example the
IP address is for the MGS node not the MDT node. So MDT will never mount on the MDT
node.
To fix the problem, use the following procedure:
IMPORTANT:
The following steps must be performed in the exact order as they appear below.
1.
Unmount HP SFS from all client nodes.
# umount /testfs
2.
Stop Heartbeat on HP SFS server nodes.
a.
Stop the Heartbeat service on all the OSS nodes:
# pdsh -w oss[1-n] service heartbeat stop
b.
Stop the Heartbeat service on the MDS and MGS nodes:
# pdsh -w mgs,mds service heartbeat stop
c.
To prevent the file system components and the Heartbeat service from automatically
starting on boot, enter the following command:
# pdsh -a chkconfig --level 345 heartbeat off
This forces you to manually start the Heartbeat service and the file system after a file
system server node is rebooted.
3.
Verify that the Lustre mount-points are unmounted on the servers.
# pdsh -a "df | grep mnt"
4.
Run the following command on the MGS node:
# tunefs.lustre --writeconf /dev/mapper/mpath
[mgs]
5.
Run the following command on the MDT node:
# tunefs.lustre --writeconf /dev/mapper/mpath
[mdt]
6.
Run this command on each OSS server node for all the mpaths which that node normally
mounts:
# tunefs.lustre --writeconf /dev/mapper/mpath
[oss]
7.
Manually mount the MGS mpath on the MGS server. Monitor the /var/log/messages
to verify that it is mounted without any errors.
8.
Manually mount the MDT mpath on the MDT server. Monitor the /var/log/messages
to verify that there are no errors and the mount is complete. This might take several minutes.
9.
Manually mount each OST on the OSS server where it normally runs.
10.
From one client node, mount the Lustre file system. The mount initiates a file system recovery.
If the file system has a large amount of data, the recovery might take some time to complete.
The progress can be monitored from the MDT node using:
# cat /proc/fs/lustre/*/*/recovery_status
11.
After the file system is successfully mounted on the client node, unmount the file system.
12.
Verify that the problem has been resolved by generating a new debugfs dump file (as
described earlier in this section). Verify that the MDT IP address is now associated with the
MDT.
13.
Manually unmount the HP SFS mpath devices on each HP SFS server.
14.
Shut down the MDT node.
15.
Start the Heartbeat service on the MGS node:
# service heartbeat start
5.7 Testing Your Configuration
55