[Lustre-discuss] OST errors caused by residual client info?

[Jeff Johnson]

Greetings..

Is it possible that the below error can be derived from a client that 
has not been rebooted or had lustre kernel mods reloaded during a time 
when a few test file systems were built and mounted?

LustreError: 12967:0:(ldlm_lib.c:1914:target_send_reply_msg()) @@@ processing error (-19)  req at ffff81032dd2d000 x1348952525350751/t0 o8-><?>@<?>:0/0 lens 368/0 e 0 to 0 dl 1291669076 ref 1 fl Interpret:/0/0 rc -19/0
LustreError: 12967:0:(ldlm_lib.c:1914:target_send_reply_msg()) Skipped 55 previous similar messages
LustreError: 137-5: UUID 'fs-OST0058_UUID' is not available  for connect (no target)


Normally this would be a back end storage issue. In this case, the oss 
where this error is logged doesn't have an ost "OST0058". It has an ost 
"OST006d". Regardless of the ost name, the backend raid is healthy with 
no hardware errors. No other h/w errors present on the oss node (e.g.: 
mce, panic, ib/enet failures, etc).

Previous test incarnations of this filesystem were built where ost name 
was not assigned (e.g.: OSTFFFF) and was assigned upon first mount and 
connection to the mds. Is it possible that some clients have residual 
pointers or config data about the previously built file systems?

Thanks!

--Jeff