<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="text-align:left; direction:ltr;">
<div>Hi <span style="font-family: sans-serif; font-size: small;">Venkat,</span></div>
<div><span style="font-family: sans-serif; font-size: small;"><br>
</span></div>
<div><span style="font-family: sans-serif; font-size: small;">Thanks for getting back to me.</span></div>
<div><span style="font-family: sans-serif; font-size: small;"><br>
</span></div>
<div><span style="font-family: sans-serif; font-size: small;">On the cache side we're running </span>5.0.4-3 on the nsd servers and 5.0.5-2 everywhere else, including gateway nodes.</div>
<div>The home cluster is 4.2.3-22 - unfortunately we're stuck on 4.x due to the licensing but we're in the process of replacing that system.</div>
<div><br>
</div>
<div>The actual AFM seems to be behaving fine though so I'm not sure that's our issue. I guess our next job is to see if we can reproduce it in a non-AFM fileset.</div>
<div><br>
</div>
<div>Rob</div>
<div><br>
</div>
<div>On Fri, 2021-03-19 at 12:02 +0530, Venkateswara R Puvvada wrote:</div>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<div style="background-color:#FFEB9C; width:100%; border-style: solid; border-color:#9C6500; border-width:1pt; padding:2pt; font-size:10pt; line-height:12pt; font-family:'Calibri'; color:Black; text-align: left;">
<span style="color:#9C6500; font-weight:bold;">CAUTION:</span> This email originated from outside of the ICR. Do not click links or open attachments unless you recognize the sender's email address and know the content is safe.</div>
<br>
<div><font size="2" face="sans-serif">Robert,</font><br>
<br>
<font size="2" face="sans-serif">What is the scale version ? This issue may be related to these alerts.</font><br>
<br>
<a href="https://www.ibm.com/support/pages/node/6355983"><font size="3" color="blue">https://www.ibm.com/support/pages/node/6355983</font></a><br>
<a href="https://www.ibm.com/support/pages/node/6380740"><font size="2" color="blue" face="sans-serif">https://www.ibm.com/support/pages/node/6380740</font></a><br>
<br>
<font size="3">These are the recommended steps to resolve the issue, but need more details on the scale version.</font><br>
<font size="3"><br>
1. Stop all AFM filesets at cache using "mmafmctl device stop -j fileset" command.<br>
2. Perform rolling upgrade parallely at both cache and home clusters<br>
a. All nodes on home cluster to 5.0.5.6<br>
b. All gateway nodes in cache cluster to 5.0.5.6<br>
3. At home cluster, for each fileset target path, repeat below steps<br>
a. Remove .afmctl file<br>
mmafmlocal rm <fileset target path>/.afm/.afmctl<br>
b. Enable AFM<br>
mmafmconfig enable <fileset target path><br>
4. Start all AFM filesets at cache using "mmafmctl device start -j fileset" command.
</font><br>
<br>
<font size="2" face="sans-serif">~Venkat (vpuvvada@in.ibm.com)</font><br>
<br>
<br>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">From: </font><font size="1" face="sans-serif">Robert Horton <robert.horton@icr.ac.uk></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">To: </font><font size="1" face="sans-serif">"gpfsug-discuss@spectrumscale.org" <gpfsug-discuss@spectrumscale.org></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Date: </font><font size="1" face="sans-serif">03/18/2021 09:17 PM</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Subject: </font><font size="1" face="sans-serif">[EXTERNAL] [gpfsug-discuss] SpectrumScale / AFM / Singularity soft lockups</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Sent by: </font><font size="1" face="sans-serif">gpfsug-discuss-bounces@spectrumscale.org</font><br>
<hr noshade="">
<br>
<br>
<br>
<font size="3">Hello,</font><br>
<br>
<font size="3">We've recently started having an issue where processes running in a singularity container get stuck in a soft lockup and eventually the node needs to be forcibly rebooted. I have included a sample call trace below. Additionally, other (non-singularity)
processes on other nodes accessing the same fileset seem to get into the same state. It's also an AFM IW fileset just to add to the complexity ;)</font><br>
<br>
<font size="3">Does anyone have any thoughts on what might be happening / how to proceed? I'm not really sure if it's a GPFS issue or a Singularity / Kernel issue - although fact it seems to spread to other nodes would seem to suggest some GPFS involvement.
It's possible the user is doing something inadvisable with Singularity (it's difficult to work out what's happening in the Nextflow pipeline) but even if they are it would be good to find a way of preventing them taking nodes down. I'm assuming the AFM is
unlikely to be relevant - any views on that?</font><br>
<br>
<font size="3">Thanks,</font><br>
<font size="3">Rob</font><br>
<br>
<font size="3"> Call Trace:</font><br>
<font size="3">? _Z11kSFSGetattrP15KernelOperationP13gpfsVfsData_tP10gpfsNode_tiP10cxiVattr_tP12gpfs_iattr64+0x1e4/0x5d0 [mmfs26]</font><br>
<font size="3"> _ZL17refreshCacheAttrsP13gpfsVfsData_tP15KernelOperationP9cxiNode_tP10pcacheAttriPcj+0x441/0x450 [mmfs26]</font><br>
<font size="3"> _Z21pcacheHandleCollisionP13gpfsVfsData_tP15KernelOperationP10gpfsNode_tS4_PcPvP9MMFSVInfoiP10pcacheAttriS5_10PcacheModej+0xa21/0x11b0 [mmfs26]</font><br>
<font size="3"> ? _ZN6ThCond6signalEv+0x82/0x190 [mmfs26]</font><br>
<font size="3"> ? _ZN10MemoryPool6shFreeEPv9MallocUse+0x1a5/0x2a0 [mmfs26]</font><br>
<font size="3"> ? _ZL14kSFSPcacheSendP13gpfsVfsData_tP15KernelOperation7FileUIDS3_PciiPPv+0x387/0x570 [mmfs26]</font><br>
<font size="3"> ? _ZL17pcacheNeedRefresh10PcacheModejlijj+0x206/0x230 [mmfs26]</font><br>
<font size="3">_Z12pcacheLookupP13gpfsVfsData_tP15KernelOperationP10gpfsNode_tPvPcP7FilesetjjjPS5_PS4_PyPjS9_+0x1dcf/0x25c0 [mmfs26]</font><br>
<font size="3">? _Z15findFilesetByIdP15KernelOperationjjPP7Filesetj+0x4f/0xa0 [mmfs26]</font><br>
<font size="3"> _Z10gpfsLookupP13gpfsVfsData_tPvP9cxiNode_tS1_S1_PcjPS1_PS3_PyP10cxiVattr_tPjP10ext_cred_tjS5_PiS4_SD_+0x65c/0xad0 [mmfs26]</font><br>
<font size="3">gpfs_i_lookup+0x189/0x3f0 [mmfslinux]</font><br>
<font size="3"> ? _Z8gpfsLinkP13gpfsVfsData_tP9cxiNode_tS2_PvPcjjP10ext_cred_t+0x6e0/0x6e0 [mmfs26]</font><br>
<font size="3"> ? d_alloc_parallel+0x99/0x4a0</font><br>
<font size="3"> ? _Z33gpfsIsCifsBypassTraversalCheckingv+0xe2/0x130 [mmfs26]</font><br>
<font size="3"> __lookup_slow+0x97/0x150</font><br>
<font size="3"> lookup_slow+0x35/0x50</font><br>
<font size="3"> walk_component+0x1bf/0x330</font><br>
<font size="3"> ? _ZL12gpfsGetattrxP13gpfsVfsData_tP9cxiNode_tP10cxiVattr_tP12gpfs_iattr64i+0x147/0x390 [mmfs26]</font><br>
<font size="3"> path_lookupat.isra.49+0x75/0x200</font><br>
<font size="3"> filename_lookup.part.63+0xa0/0x170</font><br>
<font size="3">? strncpy_from_user+0x4f/0x1b0</font><br>
<font size="3"> vfs_statx+0x73/0xe0</font><br>
<font size="3"> __do_sys_newlstat+0x39/0x70</font><br>
<font size="3"> ? syscall_trace_enter+0x1d3/0x2c0</font><br>
<font size="3"> ? __audit_syscall_exit+0x249/0x2a0</font><br>
<font size="3"> do_syscall_64+0x5b/0x1a0</font><br>
<font size="3"> entry_SYSCALL_64_after_hwframe+0x65/0xca</font><br>
<tt><font size="3">-- </font></tt><br>
<font size="3">Robert Horton | Research Data Storage Lead</font><br>
<font size="3">The Institute of Cancer Research | 237 Fulham Road | London | SW3 6JB</font><br>
<font size="3">T +44 (0)20 7153 5350 | E </font><a href="mailto:robert.horton@icr.ac.uk"><font size="3" color="blue"><u>robert.horton@icr.ac.uk</u></font></a><font size="3">| W
</font><a href="www.icr.ac.uk"><font size="3">www.icr.ac.uk</font></a><font size="3">| Twitter @ICR_London</font><br>
<font size="3">Facebook: </font><a href="www.facebook.com/theinstituteofcancerresearch"><font size="3" color="blue"><u>www.facebook.com/theinstituteofcancerresearch</u></font></a><br>
<font size="3"><br>
The Institute of Cancer Research: Royal Cancer Hospital, a charitable Company Limited by Guarantee, Registered in England under Company No. 534147 with its Registered Office at 123 Old Brompton Road, London SW7 3RP.<br>
<br>
This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer and network.</font><tt><font size="2">_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at spectrumscale.org<br>
</font></tt><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=92LOlNh2yLzrrGTDA7HnfF8LFr55zGxghLZtvZcZD7A&m=gHmKEtEM3EvdWRefAF0Cs8N2qXPZg5flGutpiJu_bfg&s=dnKFsINgU63_3b-7i3z3uDnxnij6iT-y8L_mmYHr8IE&e="><tt><font size="2">https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=92LOlNh2yLzrrGTDA7HnfF8LFr55zGxghLZtvZcZD7A&m=gHmKEtEM3EvdWRefAF0Cs8N2qXPZg5flGutpiJu_bfg&s=dnKFsINgU63_3b-7i3z3uDnxnij6iT-y8L_mmYHr8IE&e=</font></tt></a><tt><font size="2"><br>
</font></tt><br>
<br>
<br>
</div>
</blockquote>
<div><span>
<pre>-- <br></pre>
<div style="width: 71ch;">Robert Horton | Research Data Storage Lead</div>
<div style="width: 71ch;">The Institute of Cancer Research | 237 Fulham Road | London | SW3 6JB</div>
<div style="width: 71ch;">T +44 (0)20 7153 5350 | E <a href="mailto:robert.horton@icr.ac.uk">
robert.horton@icr.ac.uk</a> | W www.icr.ac.uk | Twitter @ICR_London</div>
<div style="width: 71ch;">Facebook: <a href="www.facebook.com/theinstituteofcancerresearch">
www.facebook.com/theinstituteofcancerresearch</a></div>
<div style="width: 71ch;"></div>
</span></div>
<br clear="both">
The Institute of Cancer Research: Royal Cancer Hospital, a charitable Company Limited by Guarantee, Registered in England under Company No. 534147 with its Registered Office at 123 Old Brompton Road, London SW7 3RP.<BR>
<BR>
This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer and network.<BR>
</body>
</html>