Hello, I have a Spectrum Scale cluster with 10 nodes on the version 4.2. The cluster have maxblocksize=DEFAULT. I will migrate all nodes to 5.0.3 (online) none downtime.
But the maxblocksize is fixed on the mmlsconfig after the migration (the man have this information) maxblocksize 1M man mmchconfig Note: When you migrate a cluster from an earlier version to 5.0.0 or later, the value of maxblocksize stays the same. However, if maxblocksize was set to DEFAULT in the earlier version of the cluster, then migrating it to 5.0.0 or later sets it explicitly to 1 MiB, which was the default value in earlier versions. To change maxblocksize to the default value after migrating to 5.0.0 or later, set maxblocksize=DEFAULT (4 MiB). How Can I perform non-stop migration and after migration create a new filesystem with blocksize = 4MiB? My question is about finishing the migration and create a new filesystem with block size set to 4 MiB, its won't be possible until the maxblocksize changes. In a environment where all migration will be done without stopping the cluster, my question was if there was any alternative This behavior forces the entire cluster to stop. Regards, Rafael Cezário Damásio Cunha IT Specialist - PowerVM/AIX/Spectrum Scale Technology Support Services Global Technology Services Mobile: 55-6198122-4435 E-mail: [email protected] Scn Quadra 4, Bloco B, n.100 Brasilia, DF 70714-900 Brazil
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
