This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
gpfs:gpfs_sizing [2021/01/01 21:24] 127.0.0.1 external edit |
gpfs:gpfs_sizing [2024/06/21 17:05] (current) manu [NSD access] |
||
---|---|---|---|
Line 2: | Line 2: | ||
===== Filesystem Block size, best practice ===== | ===== Filesystem Block size, best practice ===== | ||
+ | |||
+ | Typically, metadata is between 1 and 5% of the filesystem space, but this can vary. | ||
Depending on usage, you can have different **block size** | Depending on usage, you can have different **block size** | ||
Line 47: | Line 49: | ||
|Enterprise File (Misc Projects, data sharing)| Other Storage|256KiB metadata and data| | |Enterprise File (Misc Projects, data sharing)| Other Storage|256KiB metadata and data| | ||
+ | ===== Customization ===== | ||
+ | |||
+ | ==== NSD access ==== | ||
+ | |||
+ | During NSD creation alternate node position for access to NSD. | ||
+ | If the first node is used as first node in NSD definition, then it 'll be only use and you'll reach performance problems | ||
+ | |||
+ | If only the first node is selected as first into NSD definition means every NSD task ( read/ write ... ) has to be handled by NSD server 'gpfs1' as long as he is reachable. | ||
+ | Such a configuration could cause a overload situation on the affected server. | ||
+ | |||
+ | The NSD server sequence can be adjusted online via command **mmchnsd** ( see below ): | ||
+ | https://www.ibm.com/docs/en/spectrum-scale/5.0.5?topic=disks-changing-your-nsd-configuration | ||
+ | Ex: | ||
+ | <cli prompt='#'> | ||
+ | # mmchnsd "data_nsd043:gpfs03.gpfsint.labo,gpfs04.gpfsint.labo,gpfs01.gpfsint.labo,gpfs02.gpfsint.labo" | ||
+ | </cli> | ||
+ | |||
+ | Maybe easier with a description file | ||
+ | |||
+ | <cli prompt='#'> | ||
+ | # mmlsnsd -X | ||
+ | File system Disk name NSD volume ID NSD servers | ||
+ | ------------------------------------------------------------------------------------------------ | ||
+ | cases data_nsd043 C0A80017543D01BC gpfs03.gpfsint.labo,gpfs04.gpfsint.labo,gpfs01.gpfsint.labo,gpfs02.gpfsint.labo | ||
+ | cases data_nsd044 C0A80018543CE5A2 gpfs04.gpfsint.labo,gpfs01.gpfsint.labo,gpfs02.gpfsint.labo,gpfs03.gpfsint.labo | ||
+ | cases data_nsd045 C0A80017543D01C3 gpfs01.gpfsint.labo,gpfs02.gpfsint.labo,gpfs03.gpfsint.labo,gpfs04.gpfsint.labo | ||
+ | cases data_nsd046 C0A80018543CE5A8 gpfs02.gpfsint.labo,gpfs03.gpfsint.labo,gpfs04.gpfsint.labo,gpfs01.gpfsint.labo | ||
+ | cases data_nsd047 C0A80017543D01C9 gpfs03.gpfsint.labo,gpfs04.gpfsint.labo,gpfs01.gpfsint.labo,gpfs02.gpfsint.labo | ||
+ | </cli> |