Re: [gpfsug-discuss] data replicas and metadata space used

2020-09-02 Thread Felipe Knop
Russell,   The maximum number of replicas, as specified via   mmcrfs -R MaxDataReplicas   causes space to be reserved in the inode and indirect block for the replicated disk address for each data block.   For files which are small enough to fit in the inode, it should not make a difference.   For

Re: [gpfsug-discuss] tsgskkm stuck---> what about AMD epyc support in GPFS?

2020-09-02 Thread Andrew Beattie
Giovanni,   I have clients in Australia that are running AMD ROME processors in their Visualisation nodes connected to scale 5.0.4 clusters with no issues.   Spectrum Scale doesn't differentiate between x86 processor technologies -- it only looks at x86_64 (OS support more than anything else)      

Re: [gpfsug-discuss] tsgskkm stuck---> what about AMD epyc support in GPFS?

2020-09-02 Thread Giovanni Bracco
I am curious to know about AMD epyc support by GPFS: what is the status? Giovanni Bracco On 28/08/20 14:25, Frederick Stock wrote: Not sure that Spectrum Scale has stated it supports the AMD epyc (Rome?) processors.  You may want to open a help case to determine the cause of this problem. Note

[gpfsug-discuss] data replicas and metadata space used

2020-09-02 Thread Russell Nordquist
I was reading this slide deck on GPFS metadata sizing and I ran across something http://files.gpfsug.org/presentations/2016/south-bank/D2_P2_A_spectrum_scale_metadata_dark_V2a.pdf On slide 51 it says "Max replicas for Data, multiplies the MD capacity used • Reserves space in MD for the replicas