.
Von: gpfsug-discuss-boun...@spectrumscale.org
[mailto:gpfsug-discuss-boun...@spectrumscale.org] Im Auftrag von Sven Oehme
Gesendet: Freitag, 9. Februar 2018 16:09
An: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>
Betreff: Re: [gpfsug-discuss] V5 Experience -- maxblocksize
y
-boun...@spectrumscale.org] *Im Auftrag von *Sven Oehme
> *Gesendet:* Freitag, 9. Februar 2018 15:48
>
>
> *An:* gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>
> *Betreff:* Re: [gpfsug-discuss] V5 Experience -- maxblocksize
>
>
>
> Renar,
>
>
>
> if y
<gpfsug-discuss@spectrumscale.org>
Betreff: Re: [gpfsug-discuss] V5 Experience -- maxblocksize
Renar,
if you specify the filesystem blocksize of 1M during mmcr you don't have to
restart anything. scale 5 didn't change anything on the behaviour of
maxblocksize change while the cluster is
Auftrag von *Felipe Knop
> *Gesendet:* Freitag, 9. Februar 2018 14:59
> *An:* gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>
> *Betreff:* Re: [gpfsug-discuss] V5 Experience -- maxblocksize
>
>
>
> All,
>
> Correct. There is no need to ch
uss@spectrumscale.org>
Betreff: Re: [gpfsug-discuss] V5 Experience -- maxblocksize
All,
Correct. There is no need to change the value of 'maxblocksize' for existing
clusters which are upgraded to the 5.0.0 level. If a new file system needs to
be created with a block size which exceeds the value of maxblo
All,
Correct. There is no need to change the value of 'maxblocksize' for
existing clusters which are upgraded to the 5.0.0 level. If a new file
system needs to be created with a block size which exceeds the value of
maxblocksize then the mmchconfig needs to be issued to increase the value
of
