<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="text-align:left; direction:ltr;">
<div>I cannot speak for Redhat, but the RHEL release cycles are documented: <a href="https://access.redhat.com/support/policy/updates/errata#RHEL8_and_9_Life_Cycle">
https://access.redhat.com/support/policy/updates/errata#RHEL8_and_9_Life_Cycle</a>
</div>
<div>The rule of thumb for Scale is that a new RHEL minor release will likely be supported in the Scale release or PTF following the RHEL release. There might be exceptions dending on the timing of the release dates, possible problems found in testing, etc.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christof</div>
<div><br>
</div>
<div>On Thu, 2023-08-17 at 19:58 +0200, Uwe Falke wrote:</div>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<p>thanks, ryan. <br>
</p>
<p>I would have loved to stay with RHEL 8.7, however RHEL chose to not patch the RHEL8.7 Kernel line it seems ...</p>
<p>Uwe <br>
</p>
<div class="moz-cite-prefix">On 17.08.23 18:53, Ryan Novosielski wrote:<br>
</div>
<blockquote type="cite" cite="mid:6E40DCAC-4EB1-4414-A300-86F446A934B8@rutgers.edu" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
Sorry, one more thing: while you can often upgrade from say 3.10.0-1160.92.1 to 3.10.0-1160.95.1, like the kind of upgrade you’d see within an RHEL point release — and you’ll often see an older version get updated to list support for those kinds of version
increments — you should definitely expect to potentially need to upgrade GPFS if you’re going between RHEL point releases, like 8.7 to 8.8 — those ones that change from, say, 4.18.0-425.x to 4.18.0-477.x.
<div><br>
</div>
<div>Sometimes unsupported versions will work, but often times they will not, and if you have a support contract, that difference is sort of meaningless since you wouldn’t want to run an unsupported version anyway.<br>
<div><br>
<div>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<div>On Aug 17, 2023, at 12:38, Ryan Novosielski <a class="moz-txt-link-rfc2396E" href="mailto:novosirj@rutgers.edu">
<novosirj@rutgers.edu></a> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div style="overflow-wrap: break-word;
-webkit-nbsp-mode: space; line-break:
after-white-space;">
Not supported on that GPFS version; probably need a 5.1.8.x — definitely supported on 5.1.8.1.
<div><br>
</div>
<div>Always check here before upgrading the kernel: </div>
<div><br>
</div>
<div><a href="https://www.ibm.com/docs/en/storage-scale?topic=STXKQY/gpfsclustersfaq.html" moz-do-not-send="true" class="moz-txt-link-freetext">https://www.ibm.com/docs/en/storage-scale?topic=STXKQY/gpfsclustersfaq.html</a></div>
<div><br>
<div>
<div>
<div dir="auto" style="caret-color: rgb(0, 0,
0); letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px;
text-decoration: none; overflow-wrap:
break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;">
<div dir="auto" style="caret-color: rgb(0, 0,
0); letter-spacing: normal; text-align:
start; text-indent: 0px; text-transform:
none; white-space: normal; word-spacing:
0px; -webkit-text-stroke-width: 0px;
text-decoration: none; overflow-wrap:
break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;">
<div dir="auto" style="caret-color: rgb(0,
0, 0); letter-spacing: normal; text-align:
start; text-indent: 0px; text-transform:
none; white-space: normal; word-spacing:
0px; -webkit-text-stroke-width: 0px;
text-decoration: none; overflow-wrap:
break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;">
<div dir="auto" style="caret-color: rgb(0,
0, 0); letter-spacing: normal;
text-align: start; text-indent: 0px;
text-transform: none; white-space:
normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px;
text-decoration: none; overflow-wrap:
break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;">
<div style="letter-spacing: normal;
text-align: start; text-indent: 0px;
text-transform: none; white-space:
normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px;
overflow-wrap: break-word;
-webkit-nbsp-mode: space; line-break:
after-white-space;">
--<br>
#BlackLivesMatter</div>
<div style="letter-spacing: normal;
text-align: start; text-indent: 0px;
text-transform: none; white-space:
normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px;
overflow-wrap: break-word;
-webkit-nbsp-mode: space; line-break:
after-white-space;">
____<br>
|| \\UTGERS, |---------------------------*O*---------------------------<br>
||_// the State | Ryan Novosielski - <a class="moz-txt-link-abbreviated" href="mailto:novosirj@rutgers.edu">novosirj@rutgers.edu</a><br>
|| \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus<br>
|| \\ of NJ | Office of Advanced Research Computing - MSB A555B, Newark<br>
`'</div>
</div>
</div>
</div>
</div>
</div>
<div><br>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<div>On Aug 17, 2023, at 11:54, Uwe Falke <a class="moz-txt-link-rfc2396E" href="mailto:uwe.falke@kit.edu">
<uwe.falke@kit.edu></a> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div>
<p>Hi, just to let you know: <br>
</p>
<p>building the 5.1.7.1 GPL layer for Linux Kernel 4.18.0-477.21.1.el8_8.x86_64 failed for me:</p>
<p>[...]</p>
<pre>In file included from /usr/lpp/mmfs/src/gpl-linux/cfiles.c:87,</pre>
<pre> from /usr/lpp/mmfs/src/gpl-linux/cfiles_cust.c:54:</pre>
<pre>/usr/lpp/mmfs/src/gpl-linux/cxiCache.c: In function 'pcache_nfs_have_rdirplus':</pre>
<pre>/usr/lpp/mmfs/src/gpl-linux/cxiCache.c:4011:31: error: 'NFS_INO_ADVISE_RDPLUS' undeclared (first use in this function); did you mean 'NFS_INO_ODIRECT'?</pre>
<pre> && test_bit(NFS_INO_ADVISE_RDPLUS, &NFS_I(inodeP)->flags)</pre>
<pre> ^~~~~~~~~~~~~~~~~~~~~</pre>
<pre> NFS_INO_ODIRECT</pre>
<pre>/usr/lpp/mmfs/src/gpl-linux/cxiCache.c:4011:31: note: each undeclared identifier is reported only once for each function it appears in</pre>
<pre>[...]</pre>
<div><br class="webkit-block-placeholder">
</div>
<p>If anyone managed to build that, a message would be nice, else you should expect problems.
<br>
</p>
<p>I opened a case with IBM but it is caught in the call entry ... (SF TS013920636, in case any supporter wants to look after it).
<br>
</p>
<p>Uwe<br>
</p>
<pre>-- </pre>
<pre>Karlsruhe Institute of Technology (KIT)</pre>
<pre>Steinbuch Centre for Computing (SCC)</pre>
<pre>Scientific Data Management (SDM)</pre>
<pre><br></pre>
<pre>Uwe Falke</pre>
<pre><br></pre>
<pre>Hermann-von-Helmholtz-Platz 1, Building 442, Room 187</pre>
<pre>D-76344 Eggenstein-Leopoldshafen</pre>
<pre><br></pre>
<pre>Tel: +49 721 608 28024</pre>
<pre>Email: </pre>
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:uwe.falke@kit.edu" moz-do-not-send="true">
<pre>uwe.falke@kit.edu</pre>
</a>
<pre><br></pre>
<a class="moz-txt-link-abbreviated" href="http://www.scc.kit.edu/" moz-do-not-send="true">
<pre>www.scc.kit.edu</pre>
</a>
<pre><br></pre>
<pre><br></pre>
<pre>Registered office:</pre>
<pre>Kaiserstraße 12, 76131 Karlsruhe, Germany</pre>
<pre><br></pre>
<pre>KIT – The Research University in the Helmholtz Association </pre>
</div>
_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at gpfsug.org<br>
<a class="moz-txt-link-freetext" href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org">http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre>_______________________________________________</pre>
<pre>gpfsug-discuss mailing list</pre>
<pre>gpfsug-discuss at gpfsug.org</pre>
<a class="moz-txt-link-freetext" href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org">
<pre>http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org</pre>
</a>
<pre><br></pre>
</blockquote>
<pre>-- </pre>
<pre>Karlsruhe Institute of Technology (KIT)</pre>
<pre>Steinbuch Centre for Computing (SCC)</pre>
<pre>Scientific Data Management (SDM)</pre>
<pre><br></pre>
<pre>Uwe Falke</pre>
<pre><br></pre>
<pre>Hermann-von-Helmholtz-Platz 1, Building 442, Room 187</pre>
<pre>D-76344 Eggenstein-Leopoldshafen</pre>
<pre><br></pre>
<pre>Tel: +49 721 608 28024</pre>
<pre>Email: </pre>
<a class="moz-txt-link-abbreviated" href="mailto:uwe.falke@kit.edu">
<pre>uwe.falke@kit.edu</pre>
</a>
<pre><br></pre>
<a class="moz-txt-link-abbreviated" href="http://www.scc.kit.edu">
<pre>www.scc.kit.edu</pre>
</a>
<pre><br></pre>
<pre><br></pre>
<pre>Registered office:</pre>
<pre>Kaiserstraße 12, 76131 Karlsruhe, Germany</pre>
<pre><br></pre>
<pre>KIT – The Research University in the Helmholtz Association </pre>
<pre>_______________________________________________</pre>
<pre>gpfsug-discuss mailing list</pre>
<pre>gpfsug-discuss at gpfsug.org</pre>
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org">
<pre>http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org</pre>
</a>
<pre><br></pre>
</blockquote>
</body>
</html>