[Lustre-discuss] operation 400 on unconnected MGS

Brock Palen brockp at umich.edu
Thu Aug 7 14:10:56 PDT 2008


The problem I was refering to:

With the new filesystem we just created I am getting the following  
problem,

clients loose connection to the MGS and the MGS says it evicted  
them,  machines are on the same network and there is no errors on the  
interfaces.  The MGS  says:

Lustre: MGS: haven't heard from client e8eb1779-5cea-9cc7- 
b5ae-4c5ccf54f5ca (at 141.212.31.94 at tcp) in 240 seconds. I think it's  
dead, and I am evicting it.
LustreError: 9103:0:(mgs_handler.c:538:mgs_handle()) lustre_mgs:  
operation 400 on unconnected MGS
LustreError: 9103:0:(ldlm_lib.c:1536:target_send_reply_msg()) @@@  
processing error (-107)  req at 000001002f4e3050 x24929/t0 o400-><?>@<?>: 
0/0 lens 128/0 e 0 to 0 dl 1218142953 ref 1 fl Interpret:/0/0 rc -107/0


The "operation 400 on unconnected MGS"  is the only new message I am  
not familiar with.  Once the client losses connection with the MGS I  
will see the OST's start booting the client also.


Servers are 1.6.5.1  clients are patch-less 1.6.4.1  on RHEL4.

Any insight would be great.

Brock Palen
www.umich.edu/~brockp
Center for Advanced Computing
brockp at umich.edu
(734)936-1985






More information about the lustre-discuss mailing list