<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">The peer may be stuck in the LNet health recovery queue. You may be able to check by running this on the MDS nodes:<br>
<br>
$ lnetctl debug recovery --peer<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">You could resolve the issue by deleting the peer entry from the peer tables<br>
<br>
$ lnetctl peer del --prim <a href="mailto:10.20.1.237@o2ib5">10.20.1.237@o2ib5</a><br>
<br>
Chris Horn<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">lustre-discuss <lustre-discuss-bounces@lists.lustre.org> on behalf of Thomas Roth <t.roth@gsi.de><br>
<b>Date: </b>Thursday, July 15, 2021 at 5:06 AM<br>
<b>To: </b>lustre-discuss@lists.lustre.org <lustre-discuss@lists.lustre.org><br>
<b>Subject: </b>[lustre-discuss] non-existing client in logs<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">Dear all,<br>
<br>
in the logs of our 3 MDS (Lustre 2.12.5), on NID is continously reported as missing, e.g.<br>
<br>
> LNet: 3571:0:(o2iblnd_cb.c:3397:kiblnd_check_conns()) Timed out tx for 10.20.1.237@o2ib5: 1 seconds<br>
<br>
Once upon a time, there was indeed a batch node with that IP. It has been decomissioned and switched off some time last year, but still crops up in
<br>
the logs.<br>
<br>
Recently I managed to revive the old hardware, connect it to Lustre. The MDS recognized the node. Then I umounted, which worked without a problem.<br>
Nevertheless, the NID keeps reappearing in the logs.<br>
<br>
Any way to make the MDSes understand that this box is gone for good? Perhaps install a new one with the old IP?<br>
<br>
Regards,<br>
Thomas<br>
<br>
-- <br>
--------------------------------------------------------------------<br>
Thomas Roth<br>
Department: IT<br>
Location: SB3 2.291<br>
Phone: +49-6159-71 1453 Fax: +49-6159-71 2986<br>
<br>
GSI Helmholtzzentrum für Schwerionenforschung GmbH<br>
Planckstraße 1, 64291 Darmstadt, Germany, <a href="http://www.gsi.de">http://www.gsi.de</a>
<br>
<br>
Commercial Register / Handelsregister: Amtsgericht Darmstadt, HRB 1528<br>
Managing Directors / Geschäftsführung:<br>
Professor Dr. Paolo Giubellino, Dr. Ulrich Breuer, Jörg Blaurock<br>
Chairman of the Supervisory Board / Vorsitzender des GSI-Aufsichtsrats:<br>
State Secretary / Staatssekretär Dr. Volkmar Dietz<br>
<br>
_______________________________________________<br>
lustre-discuss mailing list<br>
lustre-discuss@lists.lustre.org<br>
<a href="http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org">http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org</a>
<o:p></o:p></p>
</div>
</div>
</body>
</html>