Red Hat GLOBAL FILE SYSTEM 4.7 Guide de l'utilisateur télécharger pdf (Page 76)

Mounting and unmounting Lustre file systems on client nodes4–18

• The following message shows that the client node is attempting to connect to a server in the HP SFS

system:

kernel: Lustre: 4560:0:(import.c:310:import_select_connection())

MDC_n1044_sfsalias-mds5_MNT_client_vib: Using connection NID_16.123.123.102_UUID

In this example, the connection is to the mds5 service on server 16.123.123.102. On its own, this

message does not indicate a problem. If the connection fails, Lustre will try to connect to the backup

(peer) server in the HP SFS system after approximately 50 seconds. Lustre will continue alternating

between the primary and backup servers. It is normal to see this message for the duration of the (ten

minute) recovery process.

• The following message shows that an ARP (Address Resolution Protocol) request failed:

kernel: Lustre: 2988:0:(vibnal_cb.c:2760:kibnal_arp_done()) base_gid2port_num

failed: -256

Under load, ARP requests sometimes fail; to deal with this problem, Lustre retries the ARP request five

times. In addition, an ARP request to an HP SFS server that is down will always fail. See the previous

point for an example of a message showing details of a failed ARP request.

• The following message shows the occurrence of a problem in Lustre that may later cause file

operations to hang:

LustreError: 21207:0: (ldlm_resource.c:365:ldlm_namespace_cleanup()) Namespace

OSC_n208_sfsalias-ost188_MNT_client_vib resource refcount 4 after lock cleanup;

forcing cleanup.

If this message appears in the /var/log/messages file, reset the client node at the earliest

convenient time to prevent problems from occurring later. For more information on this problem, see

Section 7.3.5.

1 2 ... 71 72 73 74 75 76 77 78 79 80 81 ... 133 134

Pas de commentaire

Red Hat GLOBAL FILE SYSTEM 4.7 Guide de l'utilisateur Page 76