<html><body><p>Kevin, <br>Please go ahead and open a PMR. Cursorily, we don't know of an obvious known bug.<br>Thank you. <br><br><br>Steve Duersch<br>Spectrum Scale<br>845-433-7902<br>IBM Poughkeepsie, New York<br><br><br><br><br><tt>gpfsug-discuss-bounces@spectrumscale.org wrote on 01/19/2017 04:52:02 PM:<br><br>> From: gpfsug-discuss-request@spectrumscale.org</tt><br><tt>> To: gpfsug-discuss@spectrumscale.org</tt><br><tt>> Date: 01/19/2017 04:52 PM</tt><br><tt>> Subject: gpfsug-discuss Digest, Vol 60, Issue 47</tt><br><tt>> Sent by: gpfsug-discuss-bounces@spectrumscale.org</tt><br><tt>> <br>> Send gpfsug-discuss mailing list submissions to<br>> gpfsug-discuss@spectrumscale.org<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> <a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a><br>> or, via email, send a message with subject or body 'help' to<br>> gpfsug-discuss-request@spectrumscale.org<br>> <br>> You can reach the person managing the list at<br>> gpfsug-discuss-owner@spectrumscale.org<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of gpfsug-discuss digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Re: mmrepquota and group names in GPFS 4.2.2.x<br>> (Buterbaugh, Kevin L)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Thu, 19 Jan 2017 21:51:07 +0000<br>> From: "Buterbaugh, Kevin L" <Kevin.Buterbaugh@Vanderbilt.Edu><br>> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br>> Subject: Re: [gpfsug-discuss] mmrepquota and group names in GPFS<br>> 4.2.2.x<br>> Message-ID: <31F584FD-A926-4D86-B365-63EA244DEE45@vanderbilt.edu><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> Hi All,<br>> <br>> Let me try to answer some questions that have been raised by various<br>> list members?<br>> <br>> 1. I am not using nscd.<br>> 2. getent group with either a GID or a group name resolves GID?s / <br>> names that are being printed as GIDs by mmrepquota<br>> 3. The GID?s in question are all in a normal range ? i.e. some <br>> group names that are being printed by mmrepquota have GIDs ?close? <br>> to others that are being printed as GID?s<br>> 4. strace?ing mmrepquota doesn?t show anything relating to nscd or <br>> anything that jumps out at me<br>> <br>> Here?s another point ? I am 95% sure that I have a client that was <br>> running 4.2.1.1 and mmrepquota displayed the group names ? I then <br>> upgraded GPFS on it ? no other changes ? and now it?s mostly GID?s. <br>> I?m not 100% sure because output scrolled out of my terminal buffer.<br>> <br>> Thanks to all for the suggestions ? please feel free to keep them <br>> coming. To any of the GPFS team on this mailing list, at least one <br>> other person has reported the same behavior ? is this a known bug?<br>> <br>> Kevin<br>> <br>> On Jan 19, 2017, at 3:22 PM, Greg.Lehmann@csiro.au<<br>> <a href="mailto:Greg.Lehmann@csiro.au">mailto:Greg.Lehmann@csiro.au</a>> wrote:<br>> <br>> <br>> It's not something to do with the value of the GID, like being less <br>> or greater than some number?<br>> <br>> ________________________________<br>> From: gpfsug-discuss-bounces@spectrumscale.org<<a href="mailto:gpfsug-">mailto:gpfsug-</a><br>> discuss-bounces@spectrumscale.org> <gpfsug-discuss-bounces@spectrumscale.org<<br>> <a href="mailto:gpfsug-discuss-bounces@spectrumscale.org">mailto:gpfsug-discuss-bounces@spectrumscale.org</a>>> on behalf of Olaf <br>> Weiser <olaf.weiser@de.ibm.com<<a href="mailto:olaf.weiser@de.ibm.com">mailto:olaf.weiser@de.ibm.com</a>>><br>> Sent: Friday, 20 January 2017 3:16 AM<br>> To: gpfsug main discussion list<br>> Subject: Re: [gpfsug-discuss] mmrepquota and group names in GPFS 4.2.2.x<br>> <br>> in my eyes.. that's the hint .. not to wait until all 700 clients <br>> 'll have been updated .. before open PMR .. ;-) ...<br>> <br>> <br>> <br>> From: Lukas Hejtmanek <xhejtman@ics.muni.cz<<a href="mailto:xhejtman@ics.muni.cz">mailto:xhejtman@ics.muni.cz</a><br>> >><br>> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org<<br>> <a href="mailto:gpfsug-discuss@spectrumscale.org">mailto:gpfsug-discuss@spectrumscale.org</a>>><br>> Date: 01/19/2017 05:37 PM<br>> Subject: Re: [gpfsug-discuss] mmrepquota and group names in <br>> GPFS 4.2.2.x<br>> Sent by: gpfsug-discuss-bounces@spectrumscale.org<<br>> <a href="mailto:gpfsug-discuss-bounces@spectrumscale.org">mailto:gpfsug-discuss-bounces@spectrumscale.org</a>><br>> ________________________________<br>> <br>> <br>> <br>> 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 <br>> ~700 of them, it?ll be a few weeks. And to me that?s good ? I don?t<br>> consider figuring out why this is happening a waste of time and <br>> 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<br>> this public forum, I can assure you that on every 4.2.1.1 system <br>> 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 <br>> necessary. I just thought someone on the list might have an idea as<br>> to what is happening or be able to point out the obvious explanation<br>> 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<<br>> <a href="mailto:olaf.weiser@de.ibm.com">mailto:olaf.weiser@de.ibm.com</a>><<a href="mailto:olaf.weiser@de.ibm.com">mailto:olaf.weiser@de.ibm.com</a>>> wrote:<br>> ><br>> > unfortunately , I don't own a cluster right now, which has 4.2.2 <br>> to double check... SpectrumScale should resolve the GID into a name,<br>> if it find the name somewhere...<br>> ><br>> > but in your case.. I would say.. before we waste to much time in a<br>> version-mismatch issue.. finish the rolling migration, especially <br>> 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<<br>> <a href="mailto:Kevin.Buterbaugh@Vanderbilt.Edu">mailto:Kevin.Buterbaugh@Vanderbilt.Edu</a>><<a href="mailto:Kevin.Buterbaugh@Vanderbilt.Edu">mailto:Kevin.Buterbaugh@Vanderbilt.Edu</a><br>> >><br>> > To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org<<br>> <a href="mailto:gpfsug-discuss@spectrumscale.org">mailto:gpfsug-discuss@spectrumscale.org</a>><<a href="mailto:gpfsug-">mailto:gpfsug-</a><br>> discuss@spectrumscale.org>><br>> > Date: 01/19/2017 04:48 PM<br>> > Subject: Re: [gpfsug-discuss] mmrepquota and group names in<br>> GPFS 4.2.2.x<br>> > Sent by: gpfsug-discuss-bounces@spectrumscale.org<<br>> <a href="mailto:gpfsug-discuss-bounces@spectrumscale.org">mailto:gpfsug-discuss-bounces@spectrumscale.org</a>><<a href="mailto:gpfsug-">mailto:gpfsug-</a><br>> discuss-bounces@spectrumscale.org><br>> > ________________________________<br>> ><br>> ><br>> ><br>> > Hi Olaf,<br>> ><br>> > The filesystem manager runs on one of our servers, all of which <br>> are upgraded to 4.2.2.x.<br>> ><br>> > Also, I didn?t mention this yesterday but our /etc/nsswitch.conf <br>> has ?files? listed first for /etc/group.<br>> ><br>> > In addition to a mixture of GPFS versions, we also have a mixture <br>> of OS versions (RHEL 6/7). AFAIK tell with all of my testing / <br>> experimenting the only factor that seems to change the behavior of <br>> 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 <br>> 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<<br>> <a href="mailto:olaf.weiser@de.ibm.com">mailto:olaf.weiser@de.ibm.com</a>><<a href="mailto:olaf.weiser@de.ibm.com">mailto:olaf.weiser@de.ibm.com</a>>> wrote:<br>> ><br>> > have you checked, where th fsmgr runs as you have nodes with <br>> different code levels<br>> ><br>> > mmlsmgr<br>> ><br>> ><br>> ><br>> ><br>> > From: "Buterbaugh, Kevin L" <Kevin.Buterbaugh@Vanderbilt.Edu<<br>> <a href="mailto:Kevin.Buterbaugh@Vanderbilt.Edu">mailto:Kevin.Buterbaugh@Vanderbilt.Edu</a>><<a href="mailto:Kevin.Buterbaugh@Vanderbilt.Edu">mailto:Kevin.Buterbaugh@Vanderbilt.Edu</a><br>> >><br>> > To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org<<br>> <a href="mailto:gpfsug-discuss@spectrumscale.org">mailto:gpfsug-discuss@spectrumscale.org</a>><<a href="mailto:gpfsug-">mailto:gpfsug-</a><br>> discuss@spectrumscale.org>><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<<br>> <a href="mailto:gpfsug-discuss-bounces@spectrumscale.org">mailto:gpfsug-discuss-bounces@spectrumscale.org</a>><<a href="mailto:gpfsug-">mailto:gpfsug-</a><br>> discuss-bounces@spectrumscale.org><br>> > ________________________________<br>> ><br>> ><br>> ><br>> > Hi All,<br>> ><br>> > We recently upgraded our cluster (well, the servers are all <br>> upgraded; the clients are still in progress) from GPFS 4.2.1.1 to <br>> GPFS 4.2.2.1 and there appears to be a change in how mmrepquota <br>> handles group names in its? output. I?m trying to get a handle on <br>> it, because it is messing with some of my scripts and - more <br>> 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 <br>> run an ?mmrepquota -g <fs>? and if the group exists in /etc/group <br>> the group name is displayed. Of course, if the group doesn?t exist <br>> 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 <br>> most - but not all - of the time I see GID numbers instead of group <br>> names. My question is, what is the criteria GPFS 4.2.2.x is using <br>> to decide when to display a GID instead of a group name? It?s <br>> apparently *not* the length of the name of the group, because I have<br>> output in front of me where a 13 character long group name is <br>> displayed but a 7 character long group name is *not* displayed - <br>> 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 <br>> I do not want to post group names or GIDs to a public mailing list ?<br>> 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 <br>> <fs>? and then looking up the group name myself, but I want to try <br>> to understand this. Thanks?<br>> ><br>> > Kevin<br>> ><br>> ><br>> > ?<br>> > Kevin Buterbaugh - Senior System Administrator<br>> > Vanderbilt University - Advanced Computing Center for Research andEducation<br>> > Kevin.Buterbaugh@vanderbilt.edu<<a href="mailto:Kevin.Buterbaugh@vanderbilt.edu">mailto:Kevin.Buterbaugh@vanderbilt.edu</a>><<br>> <a href="mailto:Kevin.Buterbaugh@vanderbilt.edu">mailto:Kevin.Buterbaugh@vanderbilt.edu</a>>- (615)875-9633<br>> ><br>> ><br>> > _______________________________________________<br>> > gpfsug-discuss mailing list<br>> > gpfsug-discuss at spectrumscale.org<<a href="http://spectrumscale.org">http://spectrumscale.org</a>><<br>> <a href="http://spectrumscale.org">http://spectrumscale.org</a><<a href="http://spectrumscale.org/">http://spectrumscale.org/</a>>><br>> > <a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a><br>> ><br>> ><br>> ><br>> > _______________________________________________<br>> > gpfsug-discuss mailing list<br>> > gpfsug-discuss at spectrumscale.org<<a href="http://spectrumscale.org">http://spectrumscale.org</a>><<br>> <a href="http://spectrumscale.org">http://spectrumscale.org</a><<a href="http://spectrumscale.org/">http://spectrumscale.org/</a>>><br>> > <a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a><br>> ><br>> <br>> > _______________________________________________<br>> > gpfsug-discuss mailing list<br>> > gpfsug-discuss at spectrumscale.org<<a href="http://spectrumscale.org">http://spectrumscale.org</a>><br>> > <a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a><br>> <br>> <br>> --<br>> Luk?? Hejtm?nek<br>> _______________________________________________<br>> gpfsug-discuss mailing list<br>> gpfsug-discuss at spectrumscale.org<<a href="http://spectrumscale.org">http://spectrumscale.org</a>><br>> <a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a><br>> <br>> <br>> <br>> _______________________________________________<br>> gpfsug-discuss mailing list<br>> gpfsug-discuss at spectrumscale.org<<a href="http://spectrumscale.org">http://spectrumscale.org</a>><br>> <a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a><br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <<a href="http://gpfsug.org/pipermail/gpfsug-discuss/attachments/">http://gpfsug.org/pipermail/gpfsug-discuss/attachments/</a><br>> 20170119/8e599938/attachment.html><br>> <br>> ------------------------------<br>> <br>> _______________________________________________<br>> gpfsug-discuss mailing list<br>> gpfsug-discuss at spectrumscale.org<br>> <a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a><br>> <br>> <br>> End of gpfsug-discuss Digest, Vol 60, Issue 47<br>> **********************************************<br>> <br></tt><BR>
</body></html>