[Lustre-discuss] MDS overload, why?

Brian J. Murrell Brian.Murrell at Sun.COM
Fri Oct 9 04:44:57 PDT 2009


On Fri, 2009-10-09 at 10:26 +0200, Arne Brutschy wrote:
> 
> The clients showed the following error:
> > Oct  8 09:58:55 majorana kernel: LustreError: 3787:0:(events.c:66:request_out_callback()) @@@ type 4, status -5  req at f6222800 x8702488/t0 o250->MGS at 10.255.255.206@tcp:26/25 lens 304/456 e 0 to 1 dl 1254988740 ref 2 fl Rpc:N/0/0 rc 0/0
> > Oct  8 09:58:55 majorana kernel: LustreError: 3787:0:(events.c:66:request_out_callback()) Skipped 33 previous similar messages
> 
> So, my question is: what could cause such a load? The cluster was not
> exessively used... Is this a bug or a user's job that creates the load?
> How can I protect lustre against this kind of failure?

Without any more information we could not possibly know.  If you really
are getting oopses then you will need console logs (i.e. serial console)
so that we can see the stack trace.

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20091009/744dcfe2/attachment.pgp>


More information about the lustre-discuss mailing list