All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Farrell <paf@cray.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] lnet_upcall on LBUG & LU-8418
Date: Tue, 30 Aug 2016 10:16:32 -0500	[thread overview]
Message-ID: <57C5A350.30302@cray.com> (raw)

Hello,

Currently, on LBUG, Lustre tries to call a usermode helper at 
'/usr/lib/lustre/lnet_upcall'.  This is for some sort of binary that a 
user would like executed before the LBUG itself (by default, a panic) 
happens.  Lustre does not include an lnet_upcall script, so by default, 
the call fails.

Unfortunately, in extremely low memory situations, the attempt to make 
this call can hang, resulting in a node which is in an invalid state but 
will not actually panic.  This is quite problematic as it can, for 
example, prevent failover or dump collection (for debugging purposes), 
depending on how a system is configured.

LU-8418 <https://jira.hpdd.intel.com/browse/LU-8418> (from Alexander 
Zarochentsev) is looking to disable this by default.  As Andreas Dilger 
pointed out in the patch review 
(http://review.whamcloud.com/#/c/21440/), this would break any existing 
users who had put their script in that location.

But I suspect no one is actually using this feature.

So:
Do you use (or know of anyone using) the lnet_upcall feature to call a 
binary before LBUG?  (I'm looking for end user uses; if a developer is 
using it, I think it's reasonable to ask them to set it manually.)

- Patrick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20160830/12864eb6/attachment.htm>

             reply	other threads:[~2016-08-30 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 15:16 Patrick Farrell [this message]
2016-09-01 17:37 ` [lustre-devel] lnet_upcall on LBUG & LU-8418 Oleg Drokin
2016-09-20 17:04   ` James Simmons

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=57C5A350.30302@cray.com \
    --to=paf@cray.com \
    --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.