Re: [gpfsug-discuss] forcibly panic stripegroup everywhere?

2017-01-23 Thread Sven Oehme
Hi, you either need to request access to GPFS 4.2.1.0 efix16 via your PMR or need to upgrade to 4.2.2.1 both contain the fixes required. Sven On Mon, Jan 23, 2017 at 6:27 AM Sven Oehme wrote: > Aaron, > > hold a bit with the upgrade , i just got word that while 4.2.1+ most >

Re: [gpfsug-discuss] SOBAR questions

2017-01-23 Thread Marc A Kaplan
Regarding back level file systems and testing... 1. Did you know that the mmcrfs command supports --version which allows you to create a back level file system? 2. If your concern is restoring from a SOBAR backup that was made a long while ago with an old version of GPFS/sobar... I'd say that

Re: [gpfsug-discuss] mmrepquota and group names in GPFS 4.2.2.x

2017-01-23 Thread Buterbaugh, Kevin L
Hi All, Stephens’ very first question below has led me to figure out what the problem is … we have one group in /etc/group that has dozens and dozens of members … any group above that in /etc/group gets printed as a name by mmrepquota; any group below it gets printed as a GID. Wasn’t there an

Re: [gpfsug-discuss] SOBAR questions

2017-01-23 Thread Simon Thompson (Research Computing - IT Services)
Hi Mark, Thanks. I get that using it to move to a new FS version is probably beyond design. But equally, I could easily see that having to support implementing the latest FS version is a strong requirement. I.e. In a DR situation say three years down the line, it would be a new FS of (say)