From: DEGREMONT Aurelien <aurelien.degremont@cea.fr>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] Channel Bonding Debug Information
Date: Fri, 2 Oct 2015 17:03:44 +0200 [thread overview]
Message-ID: <560E9CD0.5010407@cea.fr> (raw)
In-Reply-To: <CAAqp6i2jWQheq7aeT+VkQ5+=JsuAuMTJSPewGAfvaC8r8kSf9Q@mail.gmail.com>
Hi
As discussed at last Developer Summit, my concern is about transparent
interface switching, without upper layer knowing it.
I'm not talking about a lot of interface details, others already talked
about that. I thinking about error messages and admins which are not
Lustre experts.
This is a typically timeout error message you can get on a Lustre
client. You can see a lustre target (here MDT0000) and a NID, especially
an IP address.
[4863147.960698] Lustre:
25163:0:(client.c:1939:ptlrpc_expire_one_request()) @@@ Request sent has
timed out for slow reply: [sent 1443794470/real 1443794470]
req at ffff880612a00c00 x1509752994606324/t0(0)
o38->lustre-MDT0000-mdc-ffff88062dea2000 at 10.2.10.13@o2ib:12/10 lens
400/544 e 0 to 1 dl 1443794476 ref 1 fl Rpc:XN/0/ffffffff rc 0/-1
If this error is due to LNET taking another link, either on client side
or server side and this link is sick/flacky/buggy, ... *this should not
be silent*! Ideally this NID should be updated in this error message to
reflect the route change.
I do not have a strong opinion on the way this error should be reported,
but I just wanted the case where : the network error is reported only in
debug message and this error message is displayed as-is, without any
idea that LNET did some magic stuff that failed.
Aur?lien
Le 28/09/2015 21:30, Amir Shehata a ?crit :
> Hello,
>
> As a followup on the discussion in the LAD developer summit, regarding
> ensuring that there is enough debug information provided as part of
> the Channel Bonding solution, I'm sending this email to ask for ideas
> on what type of debug information you would like to see.
>
> thanks
> amir
>
>
> _______________________________________________
> lustre-devel mailing list
> lustre-devel at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20151002/4f6a5726/attachment.htm>
prev parent reply other threads:[~2015-10-02 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 19:30 [lustre-devel] Channel Bonding Debug Information Amir Shehata
2015-09-29 21:10 ` Ashish Purkar
2015-10-01 14:31 ` Olaf Weber
2015-10-02 15:03 ` DEGREMONT Aurelien [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=560E9CD0.5010407@cea.fr \
--to=aurelien.degremont@cea.fr \
--cc=lustre-devel@lists.lustre.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.