I admit I didn’t do a whole lot of troubleshooting. We don’t run NFS so I can’t
speak about that.
Initially the server looked like it came back ok, albeit “Node starting up..”
was observed in the output of mmlscluster –ces. At that time I was not sure if
that was a) expected behaviour and/or
>
> I would have though that usage in fileset predictHPC would also go against
> the group fileset
quota-wise these filesets are "siblings",
don't be fooled by the hierarchy formed by namespace linking.
hth
-- Peter
On 2016 Dec 3. md, at 04:51 st, J. Eric Wonderley wrote:
> Hi Michael:
>
Ken Hill wrote:
> Hello Stephen,>>There are three licensing models for Spectrum Scale | GPFS:>>Server>FPO>Client>>think the thing you might be missing is the associated cost per function.
What adds to this debate is that there is now (>=4.2.2) a new licensing model available that is capacity
I don't know if this applies her but I seem to recall an issue with CentOS
7 (newer 3.X and on kernels), Broadwell processors and GPFS where GPFS
upset SMAP and would eventually get the node expelled. I think this may be
fixed in newer GPFS releases but the fix is to boot the kernel with the
Thanks Sander. That's disconcerting...yikes! Sorry for your trouble but
thank you for sharing.
I'm surprised this didn't shake out during testing of gpfs 3.5 and 4.1.
I wonder if in light of this it's wise to do the clients first? My logic
being that there's clearly an example here of 4.1
