<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none"><!--P{margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>It's not something to do with the value of the GID, like being less or greater than some number?<br>
</p>
<div style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> gpfsug-discuss-bounces@spectrumscale.org <gpfsug-discuss-bounces@spectrumscale.org> on behalf of Olaf Weiser <olaf.weiser@de.ibm.com><br>
<b>Sent:</b> Friday, 20 January 2017 3:16 AM<br>
<b>To:</b> gpfsug main discussion list<br>
<b>Subject:</b> Re: [gpfsug-discuss] mmrepquota and group names in GPFS 4.2.2.x</font>
<div> </div>
</div>
<div>
<div><font size="2" face="sans-serif">in my eyes.. that's the hint .. not to wait until all 700 clients 'll have been updated .. before open PMR .. ;-) ...</font><br>
<br>
<br>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">From: </font><font size="1" face="sans-serif">Lukas Hejtmanek <xhejtman@ics.muni.cz></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 05:37 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>
<tt><font size="2">Just leting know, I see the same problem with 4.2.2.1 version. mmrepquota<br>
resolves only some of group names.<br>
<br>
On Thu, Jan 19, 2017 at 04:25:20PM +0000, Buterbaugh, Kevin L wrote:<br>
> Hi Olaf,<br>
> <br>
> We will continue upgrading clients in a rolling fashion, but with ~700 of them, it’ll be a few weeks. And to me that’s good … I don’t consider figuring out why this is happening a waste of time and therefore having systems on both versions is a good thing.<br>
> <br>
> While I would prefer not to paste actual group names and GIDs into this public forum, I can assure you that on every 4.2.1.1 system that I have tried this on:<br>
> <br>
> 1. mmrepquota reports mostly GIDs, only a few group names<br>
> 2. /etc/nsswitch.conf says to look at files first<br>
> 3. the GID is in /etc/group<br>
> 4. length of group name doesn’t matter<br>
> <br>
> I have a support contract with IBM, so I can open a PMR if necessary. I just thought someone on the list might have an idea as to what is happening or be able to point out the obvious explanation that I’m missing. ;-)<br>
> <br>
> Thanks…<br>
> <br>
> Kevin<br>
> <br>
> On Jan 19, 2017, at 10:05 AM, Olaf Weiser <olaf.weiser@de.ibm.com<</font></tt><a href="mailto:olaf.weiser@de.ibm.com"><tt><font size="2">mailto:olaf.weiser@de.ibm.com</font></tt></a><tt><font size="2">>> wrote:<br>
> <br>
> 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...<br>
> <br>
> 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<br>
> meanwhile -I'll try to find a way for me here to setup up an 4.2.2. cluster<br>
> cheers<br>
> <br>
> <br>
> <br>
> From: "Buterbaugh, Kevin L" <Kevin.Buterbaugh@Vanderbilt.Edu<</font></tt><a href="mailto:Kevin.Buterbaugh@Vanderbilt.Edu"><tt><font size="2">mailto:Kevin.Buterbaugh@Vanderbilt.Edu</font></tt></a><tt><font size="2">>><br>
> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org<</font></tt><a href="mailto:gpfsug-discuss@spectrumscale.org"><tt><font size="2">mailto:gpfsug-discuss@spectrumscale.org</font></tt></a><tt><font size="2">>><br>
> Date: 01/19/2017 04:48 PM<br>
> Subject: Re: [gpfsug-discuss] mmrepquota and group names in GPFS 4.2.2.x<br>
> Sent by: gpfsug-discuss-bounces@spectrumscale.org<</font></tt><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org"><tt><font size="2">mailto:gpfsug-discuss-bounces@spectrumscale.org</font></tt></a><tt><font size="2">><br>
> ________________________________<br>
> <br>
> <br>
> <br>
> Hi Olaf,<br>
> <br>
> The filesystem manager runs on one of our servers, all of which are upgraded to 4.2.2.x.<br>
> <br>
> Also, I didn’t mention this yesterday but our /etc/nsswitch.conf has “files” listed first for /etc/group.<br>
> <br>
> 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.<br>
> <br>
> Other ideas, anyone? Is anyone else in a similar situation and can test whether they see similar behavior?<br>
> <br>
> Thanks...<br>
> <br>
> Kevin<br>
> <br>
> On Jan 19, 2017, at 2:45 AM, Olaf Weiser <olaf.weiser@de.ibm.com<</font></tt><a href="mailto:olaf.weiser@de.ibm.com"><tt><font size="2">mailto:olaf.weiser@de.ibm.com</font></tt></a><tt><font size="2">>> wrote:<br>
> <br>
> have you checked, where th fsmgr runs as you have nodes with different code levels<br>
> <br>
> mmlsmgr<br>
> <br>
> <br>
> <br>
> <br>
> From: "Buterbaugh, Kevin L" <Kevin.Buterbaugh@Vanderbilt.Edu<</font></tt><a href="mailto:Kevin.Buterbaugh@Vanderbilt.Edu"><tt><font size="2">mailto:Kevin.Buterbaugh@Vanderbilt.Edu</font></tt></a><tt><font size="2">>><br>
> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org<</font></tt><a href="mailto:gpfsug-discuss@spectrumscale.org"><tt><font size="2">mailto:gpfsug-discuss@spectrumscale.org</font></tt></a><tt><font size="2">>><br>
> Date: 01/18/2017 04:57 PM<br>
> Subject: [gpfsug-discuss] mmrepquota and group names in GPFS 4.2.2.x<br>
> Sent by: gpfsug-discuss-bounces@spectrumscale.org<</font></tt><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org"><tt><font size="2">mailto:gpfsug-discuss-bounces@spectrumscale.org</font></tt></a><tt><font size="2">><br>
> ________________________________<br>
> <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<br>
> <br>
> <br>
> —<br>
> Kevin Buterbaugh - Senior System Administrator<br>
> Vanderbilt University - Advanced Computing Center for Research and Education<br>
> Kevin.Buterbaugh@vanderbilt.edu<</font></tt><a href="mailto:Kevin.Buterbaugh@vanderbilt.edu"><tt><font size="2">mailto:Kevin.Buterbaugh@vanderbilt.edu</font></tt></a><tt><font size="2">>- (615)875-9633<br>
> <br>
> <br>
> _______________________________________________<br>
> gpfsug-discuss mailing list<br>
> gpfsug-discuss at spectrumscale.org<</font></tt><a href="http://spectrumscale.org/"><tt><font size="2">http://spectrumscale.org</font></tt></a><tt><font size="2">><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>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> gpfsug-discuss mailing list<br>
> gpfsug-discuss at spectrumscale.org<</font></tt><a href="http://spectrumscale.org/"><tt><font size="2">http://spectrumscale.org</font></tt></a><tt><font size="2">><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>
> <br>
<br>
> _______________________________________________<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>
<br>
<br>
-- <br>
Lukáš Hejtmánek<br>
_______________________________________________<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>
</div>
<br>
</div>
</div>
</body>
</html>