[gpfsug-discuss] "csm_resync_needed" after upgrading to GPFS v5.0.4-2

[Caubet Serrabou Marc (PSI)]

Hi Norbert,


thanks a lot for for answering.


The nodes are running RHEL7.7 (Kernel 3.10.0-1062.12.1.el7.x86_64). The previous version was 5.0.3-2.

I restarted mmsysmoncontrol (I kept usesharedlib=1 as this is RHEL). Restarting it, it cleans mmhealth messages as expected, let's see whether this is repeated or not but it might take several minutes.


Just add that when I had a mix of 5.0.3-2 and 5.0.4-2 I received some 'stale_mount' messages (from GPFSGUI) for a remote cluster filesystem mountpoints, but apparently everything worked fine. After upgrading everything to v5.0.4-2 looks like the same nodes report the 'csm_resync_needed' instead (no more 'stale_mount' errors seen since then). I am not sure whether this is related or not but might be a hint if this is related.


Best regards,

Marc

_________________________________________________________
Paul Scherrer Institut
High Performance Computing & Emerging Technologies
Marc Caubet Serrabou
Building/Room: OHSA/014
Forschungsstrasse, 111
5232 Villigen PSI
Switzerland

Telephone: +41 56 310 46 67
E-Mail: marc.caubet at psi.ch
________________________________
From: gpfsug-discuss-bounces at spectrumscale.org <gpfsug-discuss-bounces at spectrumscale.org> on behalf of Norbert Schuld <NSCHULD at de.ibm.com>
Sent: Monday, April 6, 2020 2:25:22 PM
To: gpfsug main discussion list
Subject: Re: [gpfsug-discuss] "csm_resync_needed" after upgrading to GPFS v5.0.4-2


Hi,

are the nodes running on AIX? If so my advice would be to change /var/mmfs/mmsysmon/mmsysmonitor.conf to read
[InterNodeEventing]
usesharedlib = 0

and the do a "mmsysmoncontrol restart".

What was the min. release level before the upgrade?

For most other cases a "mmsysmoncontrol restart" on the affected nodes + cluster manager node should do.

Mit freundlichen Grüßen / Kind regards

Norbert Schuld



[Inactive hide details for "Caubet Serrabou Marc (PSI)" ---06.04.2020 13:36:28---Hi all, after upgrading one of the clusters to]"Caubet Serrabou Marc (PSI)" ---06.04.2020 13:36:28---Hi all, after upgrading one of the clusters to GPFS v5.0.4-2 and setting "minReleaseLevel 5.0.4.0" I

From: "Caubet Serrabou Marc (PSI)" <marc.caubet at psi.ch>
To: "gpfsug-discuss at spectrumscale.org" <gpfsug-discuss at spectrumscale.org>
Date: 06.04.2020 13:36
Subject: [EXTERNAL] [gpfsug-discuss] "csm_resync_needed" after upgrading to GPFS v5.0.4-2
Sent by: gpfsug-discuss-bounces at spectrumscale.org

________________________________



Hi all,

after upgrading one of the clusters to GPFS v5.0.4-2 and setting "minReleaseLevel 5.0.4.0" I started to see random "csm_resync_needed" errors on some nodes. This can be easily cleared with "mmhealth node show --resync", however after some minutes the error re-appears.
Apparently, no errors in the log files and no apparent problems other than the "csm_resync_needed" error.

Before opening a support case, any hints about what could be the reason of that and whether I should worry about it? I would like to clarify what's going on before upgrading the main cluster.

Thanks a lot,
Marc

_________________________________________________________
Paul Scherrer Institut
High Performance Computing & Emerging Technologies
Marc Caubet Serrabou
Building/Room: OHSA/014
Forschungsstrasse, 111
5232 Villigen PSI
Switzerland

Telephone: +41 56 310 46 67
E-Mail: marc.caubet at psi.ch_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20200406/f8be561a/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: graycol.gif
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20200406/f8be561a/attachment-0002.gif>