Troubleshooting7–10
In the following example, the output from a fully dual-connected configuration is shown; in this example
delta6 is the client node:
[root@delta6 ~]# lctl --net tcp peer_list
12345-10.128.0.72@tcp [1]10.128.0.61->10.128.0.72:988 #3
12345-10.128.0.72@tcp [0]10.128.8.61->10.128.8.72:988 #3
12345-10.128.0.73@tcp [1]10.128.0.61->10.128.0.73:988 #3
12345-10.128.0.73@tcp [0]10.128.8.61->10.128.8.73:988 #3
12345-10.128.0.74@tcp [1]10.128.0.61->10.128.0.74:988 #3
12345-10.128.0.74@tcp [0]10.128.8.61->10.128.8.74:988 #3
Only HP SFS servers that are actively serving a device will be shown.
To list each of the connections, enter the following command:
[root@delta6 root]# lctl --net tcp conn_list
[12345-10.128.0.72@tcp O[1]10.128.8.61->10.128.8.72:988 262142/262142 nonagle
12345-10.128.0.72@tcp I[1]10.128.8.61->10.128.8.72:988 262142/262142 nonagle
12345-10.128.0.72@tcp C[1]10.128.8.61->10.128.8.72:988 262142/262142 nonagle
12345-10.128.0.72@tcp O[0]10.128.0.61->10.128.0.72:988 262142/262142 nonagle
12345-10.128.0.72@tcp I[0]10.128.0.61->10.128.0.72:988 262142/262142 nonagle
12345-10.128.0.72@tcp C[0]10.128.0.61->10.128.0.72:988 262142/262142 nonagle
12345-10.128.0.73@tcp O[1]10.128.8.61->10.128.8.73:988 262142/262142 nonagle
12345-10.128.0.73@tcp I[1]10.128.8.61->10.128.8.73:988 262142/262142 nonagle
12345-10.128.0.73@tcp C[1]10.128.8.61->10.128.8.73:988 262142/262142 nonagle
12345-10.128.0.73@tcp O[0]10.128.0.61->10.128.0.73:988 262142/262142 nonagle
12345-10.128.0.73@tcp I[0]10.128.0.61->10.128.0.73:988 262142/262142 nonagle
12345-10.128.0.73@tcp C[0]10.128.0.61->10.128.0.73:988 262142/262142 nonagle
12345-10.128.0.74@tcp O[1]10.128.8.61->10.128.8.74:988 262142/262142 nonagle
12345-10.128.0.74@tcp I[1]10.128.8.61->10.128.8.74:988 262142/262142 nonagle
12345-10.128.0.74@tcp C[1]10.128.8.61->10.128.8.74:988 262142/262142 nonagle
12345-10.128.0.74@tcp O[0]10.128.0.61->10.128.0.74:988 262142/262142 nonagle
12345-10.128.0.74@tcp I[0]10.128.0.61->10.128.0.74:988 262142/262142 nonagle
12345-10.128.0.74@tcp C[0]10.128.0.61->10.128.0.74:988 262142/262142 nonagle
To list the interfaces that may be used for interaction with Lustre file systems, enter the following command:
[root@delta6 root]# lctl --net tcp interface_list
10.128.0.61: (10.128.0.61/255.255.255.0) npeer 0 nroute 3
10.128.8.61: (10.128.8.61/255.255.255.0) npeer 0 nroute 3
The only interfaces that will be listed are the interfaces that are explicitly named in the options lnet
settings in the /etc/modprobe.conf.lustre or /etc/modules.conf.lustre file.
7.4 Miscellaneous issues
This section contains information on miscellaneous issues that may arise when client nodes are using Lustre
file systems:
The section is organized as follows:
• socknal_cb.c EOF warning (Section 7.4.1)
7. 4 . 1 s o c k n a l _ c b. c E O F w a r n i n g
A message similar to the following may occasionally be displayed on one or more client nodes:
Jun 29 14:38:21 delta65 kernel: Lustre:
2473:(socknal_cb.c:1508:ksocknal_process_receive()) [00000101fd7e6000]
EOF from 0xa800008 ip 10.128.0.8:988
This problem may be caused by incorrect settings in the /etc/hosts file on a client node, or by the fact
that two (or more) client nodes are sharing an IP address.
If this occurs, examine the /etc/hosts file on the client nodes to verify that they are correctly set up. The
hostname must not be mapped to 127.0.0.1, and no two client nodes can have the same IP address.
Kommentare zu diesen Handbüchern