HP StorageWorks Scalable File Share - Manual (Page 62)

NOTE: Use the appropriate device in place of /dev/mapper/mpath?
b. For example, if the --dryrun command returned:
Parameters: mgsnode=172.31.80.1@o2ib mgsnode=172.31.80.2@o2ib
failover.node=172.31.80.1@o2ib
Run:
tunefs.lustre --erase-params --param="mgsnode=172.31.80.1@o2ib mgsnode=172.31.80.2@o2ib
failover.node=172.31.80.1@o2ib mdt.group_upcall=NONE" --writeconf /dev/mapper/mpath?
4. Manually mount mgs on the MGS node:
# mount /mnt/mgs
5. Manually mount mds on the MDS node:
# mount /mnt/mds
In the MDS /var/log/messages file, look for a message similar to the following:
kernel: Lustre: Setting parameter testfs-MDT0000.mdt.group_upcall in log testfs-MDT0000
This indicates the change is successful.
6. Unmount /mnt/mdt and /mnt/mgs from MDT and MDS respectively.
7. Restart the HP SFS server in the normal way using Heartbeat.
It will take time for the OSSs to rebuild the configuration data and reconnect with the MDS. After
the OSSs connect, the client nodes can mount the Lustre file systems. On the MDS, watch the
messages file for the following entries for each OST:
mds kernel: Lustre: MDS testfs-MDT0000: testfs-OST0001_UUID now active, resetting orphans
7.6 Configuring the mlocate Package on Client Nodes
The mlocate package might be installed on your system. This package is typically set up to run
as a periodic job under the cron daemon. To prevent the possibility of a find command executing
on the global file system of all clients simultaneously, HP recommends adding lustre to the list
of file system types that mlocate ignores. Do this by adding lustre to the PRUNEFS list in /etc/
updatedb.conf
.
7.7 System Behavior After LBUG
A severe Lustre software bug, or LBUG, might occur occasionally on file system servers or clients.
The presence of an LBUG can be identified by the string LBUG in dmesg or /var/log/messages
output for the currently booted system. While a system can continue to operate after some LBUGs,
a system that has encountered an LBUG should be rebooted at the earliest opportunity. By default,
a system will not panic when an LBUG is encountered. If you want a panic to take place when
an LBUG is seen, run the following command one time on a server or client before Lustre has
been started. This line will then be added to your /etc/modprobe.conf file:
echo "options libcfs libcfs_panic_on_lbug=1" >> /etc/modprobe.conf
After this change, the panic on LBUG behavior will be enabled the next time Lustre is started,
or the system is booted.
7.8 SELinux Support
Lustre does not support SELinux on servers or clients. SELinux is disabled in the Kickstart
template provided with HP SFS G3.2-0.
62 Known Issues and Workarounds