[gpfsug-discuss] Node in cluster but not in cluster

[Christopher Black]

I'd try running the mmdelnode process from a different node (we use cluster
manager, mmlsmgr). Ensure the target node to be removed is unreachable from
system where you run mmdelnode by either shutting host down or setting up a
null route from cluster manager. After mmdelnode'ing, fix networking, and
mmaddnode.
Re CPU compatibility, unsure about Zen5, but we have gpfs 5.1.x.x running
on AMD Zen4.

Best,
Chris

On Tue, Jun 24, 2025 at 12:56 PM Jonathan Buzzard <
jonathan.buzzard at strath.ac.uk> wrote:

> On 24/06/2025 16:59, Achim Rehor wrote:
> >
> > I think the node was not added to the cluster, but some changes on the
> > node itself took place already (like creating /var/mmfs/gen ... and
> > possibly others)
> >
> > There is/was a chapter/appendix to the GPFS Adminstration Guide, telling
> > how to permanently remove GPFS  from a node,   that might help  on how
> > to stop the mmaddnode command  to cope with a node already belonging to
> > a cluster ...
> >
>
> I removed the GPFS packages from the node, nuked /var/mmfs and /usr/lpp
> reinstalled GPFS and that clears the issue but it is stuck again
>
> There is a tsgskkm process running at 100%, been running 15 minutes now :-(
>
> Before I go any further I am going to presume GPFS is fine on Zen5 CPUs?
> Specifically dual EPYC 9555. The node is running 5.2.2-1
>
>
> JAB.
>
> --
> Jonathan A. Buzzard                         Tel: +44141-5483420
> HPC System Administrator, ARCHIE-WeSt.
> University of Strathclyde, John Anderson Building, Glasgow. G4 0NG
>
>
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at gpfsug.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
>

-- 

This message is for the recipient’s use only, and may contain 
confidential, privileged or protected information. Any unauthorized use or 
dissemination of this communication is prohibited. If you received this 
message in error, please immediately notify the sender and destroy all 
copies of this message. The recipient should check this email and any 
attachments for the presence of viruses, as we accept no liability for any 
damage caused by any virus transmitted by this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20250624/db614c72/attachment.htm>