[gpfsug-discuss] mmlsnode: Unable to determine the local node identity.
Jaime Pinto
pinto at scinet.utoronto.ca
Wed Feb 10 19:26:56 GMT 2016
Dear group
I'm trying to deal with this in the most elegant way possible:
Once upon the time there were nodeA and nodeB in the cluster, on a
'onDemand manual HA' fashion.
* nodeA died, so I migrated the whole OS/software/application stack
from backup over to 'nodeB', IP/hostname, etc, hence 'old nodeB'
effectively became the new nodeA.
* Getting the new nodeA to rejoin the cluster was already a pain, but
through a mmdelnode and mmaddnode operation we eventually got it to
mount gpfs.
Well ...
* Old nodeA is now fixed and back on the network, and I'd like to
re-purpose it as the new standby nodeB (IP and hostname already
applied). As the subject say, I'm now facing node identity issues.
From the FSmgr I already tried to del/add nodeB, even nodeA, etc,
however GPFS seems to keep some information cached somewhere in the
cluster.
* At this point I even turned old nodeA into a nodeC with a different
IP, etc, but that doesn't help either. I can't even start gpfs on nodeC.
Question: what is the appropriate process to clean this mess from the
GPFS perspective?
I can't touch the new nodeA. It's highly committed in production already.
Thanks
Jaime
************************************
---
Jaime Pinto
SciNet HPC Consortium - Compute/Calcul Canada
www.scinet.utoronto.ca - www.computecanada.org
University of Toronto
256 McCaul Street, Room 235
Toronto, ON, M5T1W5
P: 416-978-2755
C: 416-505-1477
----------------------------------------------------------------
This message was sent using IMP at SciNet Consortium, University of Toronto.
More information about the gpfsug-discuss
mailing list