<font size=2 face="sans-serif">unfortunately , I don't own a cluster right
now, which has 4.2.2 to double check... SpectrumScale should resolve the
GID into a name, if it find the name somewhere... </font><br><br><font size=2 face="sans-serif">but in your case.. I would say.. before
we waste to much time in a version-mismatch issue.. finish the rolling
migration, especially RHEL .. and then we continue </font><br><font size=2 face="sans-serif">meanwhile -I'll try to find a
way for me here to setup up an 4.2.2. cluster</font><br><font size=2 face="sans-serif">cheers</font><br><br><br><br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Buterbaugh, Kevin
L" <Kevin.Buterbaugh@Vanderbilt.Edu></font><br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">gpfsug main discussion
list <gpfsug-discuss@spectrumscale.org></font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">01/19/2017 04:48 PM</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [gpfsug-discuss]
mmrepquota and group names in GPFS 4.2.2.x</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>Hi Olaf, </font><br><br><font size=3>The filesystem manager runs on one of our servers, all
of which are upgraded to 4.2.2.x.</font><br><br><font size=3>Also, I didn’t mention this yesterday but our /etc/nsswitch.conf
has “files” listed first for /etc/group.</font><br><br><font size=3>In addition to a mixture of GPFS versions, we also have
a mixture of OS versions (RHEL 6/7). AFAIK tell with all of my testing
/ experimenting the only factor that seems to change the behavior of mmrepquota
in regards to GIDs versus group names is the GPFS version.</font><br><br><font size=3>Other ideas, anyone? Is anyone else in a similar
situation and can test whether they see similar behavior?</font><br><br><font size=3>Thanks...</font><br><br><font size=3>Kevin</font><br><br><font size=3>On Jan 19, 2017, at 2:45 AM, Olaf Weiser <</font><a href=mailto:olaf.weiser@de.ibm.com><font size=3 color=blue><u>olaf.weiser@de.ibm.com</u></font></a><font size=3>>
wrote:</font><br><br><font size=2 face="sans-serif">have you checked, where th fsmgr runs
as you have nodes with different code levels</font><font size=3><br></font><font size=2 face="sans-serif"><br>mmlsmgr </font><font size=3><br><br><br><br></font><font size=1 color=#5f5f5f face="sans-serif"><br>From: </font><font size=1 face="sans-serif">"Buterbaugh,
Kevin L" <</font><a href=mailto:Kevin.Buterbaugh@Vanderbilt.Edu><font size=1 color=blue face="sans-serif"><u>Kevin.Buterbaugh@Vanderbilt.Edu</u></font></a><font size=1 face="sans-serif">></font><font size=1 color=#5f5f5f face="sans-serif"><br>To: </font><font size=1 face="sans-serif">gpfsug
main discussion list <</font><a href="mailto:gpfsug-discuss@spectrumscale.org"><font size=1 color=blue face="sans-serif"><u>gpfsug-discuss@spectrumscale.org</u></font></a><font size=1 face="sans-serif">></font><font size=1 color=#5f5f5f face="sans-serif"><br>Date: </font><font size=1 face="sans-serif">01/18/2017
04:57 PM</font><font size=1 color=#5f5f5f face="sans-serif"><br>Subject: </font><font size=1 face="sans-serif">[gpfsug-discuss]
mmrepquota and group names in GPFS 4.2.2.x</font><font size=1 color=#5f5f5f face="sans-serif"><br>Sent by: </font><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org"><font size=1 color=blue face="sans-serif"><u>gpfsug-discuss-bounces@spectrumscale.org</u></font></a><font size=3><br></font><hr noshade><font size=3><br><br><br>Hi All, <br><br>We recently upgraded our cluster (well, the servers are all upgraded; the
clients are still in progress) from GPFS 4.2.1.1 to GPFS 4.2.2.1 and there
appears to be a change in how mmrepquota handles group names in its’ output.
I’m trying to get a handle on it, because it is messing with some
of my scripts and - more importantly - because I don’t understand the
behavior.<br><br>From one of my clients which is still running GPFS 4.2.1.1 I can run an
“mmrepquota -g <fs>” and if the group exists in /etc/group the
group name is displayed. Of course, if the group doesn’t exist in
/etc/group, the GID is displayed. Makes sense.<br><br>However, on my servers which have been upgraded to GPFS 4.2.2.1 most -
but not all - of the time I see GID numbers instead of group names. My
question is, what is the criteria GPFS 4.2.2.x is using to decide when
to display a GID instead of a group name? It’s apparently *not*
the length of the name of the group, because I have output in front of
me where a 13 character long group name is displayed but a 7 character
long group name is *not* displayed - its’ GID is instead (and yes, both
exist in /etc/group).<br><br>I know that sample output would be useful to illustrate this, but I do
not want to post group names or GIDs to a public mailing list … if you
want to know what those are, you’ll have to ask Vladimir Putin… ;-)<br><br>I am in the process of updating scripts to use “mmrepquota -gn <fs>”
and then looking up the group name myself, but I want to try to understand
this. Thanks…<br><br>Kevin</font><br><font size=3><br></font><br><font size=3>—</font><br><font size=3>Kevin Buterbaugh - Senior System Administrator</font><br><font size=3>Vanderbilt University - Advanced Computing Center for
Research and Education</font><br><a href=mailto:Kevin.Buterbaugh@vanderbilt.edu><font size=3 color=blue><u>Kevin.Buterbaugh@vanderbilt.edu</u></font></a><font size=3>- (615)875-9633</font><br><br><br><tt><font size=2>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size=2>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size=2><br></font></tt><br><br><BR>