Troubleshooting7–4
• The interconnect may not be functioning correctly.
If all of the MDS and OST services associated with the file system are available and the client node
has been configured correctly but is still failing to mount or unmount a file system, ensure that the
interconnect that the client node is using to communicate with the servers is functioning correctly.
If none of the above considerations provides a solution to the failure of the mount or unmount operation,
reboot the client node. Rebooting the node unmounts all mounted Lustre file systems. If the failed operation
was a mount operation, you can attempt to mount the file system again when the server has rebooted.
7.2.2 The sfsmount command reports device or resource busy
When a Myrinet interconnect is used to connect the client nodes to the HP SFS system, Lustre uses
GM port 4 on the client nodes. If there is a GM/MPICH application running on the client node, the MPICH
software may use GM port 4, and the client node will not be able to mount the Lustre file system. When this
problem occurs, a message similar to the following is displayed:
# sfsmount delta/deltaone
sfsmount: mount error 32.
mount.lustre: mount(0xdd48fa1c@gm0,0xdd48faaa@gm0:/delta-mds1/client_gm,
/mnt/deltaone) failed: No such device
mds nid 0: 0xdd48fa1c@gm
mds nid 1: 0xdd48faaa@gm
mds name: delta-mds1
profile: client_gm
options: rw,acl,user_xattr
Are the lustre modules loaded?
Check /etc/modules.conf and /proc/filesystems
To determine the exact source of the error, examine the dsmeg file on the client node, by entering the
following command:
# dmesg | grep -v "Unknown symbol"
.
.
.
GM: NOTICE: li/jointfilesconvert/261981/bgm/gm_open.c:312:_gm_open():kernel
GM: Could not open port state in kernel.
LustreError: 13304:0:(gmlnd_api.c:172:gmnal_startup()) Can't open GM port 4: 5
(busy)
LustreError: Error -5 starting up LNI gm
LustreError: 13304:0:(events.c:621:ptlrpc_init_portals()) network
initialisation failed
#
You can verify that port 4 is in use on the client by entering the following command:
# /opt/gm/bin/gm_board_info|grep -i busy
0: BUSY 3230 (this process [gm_board_info])
1: BUSY 2125
2: BUSY 2815
4: BUSY 2822 !!port 4 is busy here
5: BUSY 2823
6: BUSY 2836
You can prevent this problem from occurring by configuring Lustre to use a different port on the client, as
described here. To change the configuration, you must edit the /etc/modules.conf file on all of the
client nodes using the Myrinet interconnect, and on all of the servers in the HP SFS system. You must also
change the RAM disk image on the HP SFS Object Storage Servers so that the change will not be lost when
a server is next booted.
Comentarios a estos manuales