A fix is available
APAR status
Closed as program error.
Error description
When deploying a GPFS cluster on PureApplication System using the virtual application pattern, you can specify the block size for the filesystem (s) within that cluster. The default block size is 256 KB, which is typically recommended. The block size of each filesystem within the cluster must be <= maxblocksize on the GPFS cluster. By default GPFS server cluster maxblocksize is set to 1 MB, but the GPFS virtual application pattern automatically increases the cluster maxblocksize when a file system is created with a block size larger than 1MB. However the GPFS client cluster (which is created and used by the virtual machines that use the GPFS client policy to mount a GPFS filesystem from the GPFS cluster) also has a maxblocksize set, again by default to 1 MB. This client cluster maxblocksize value cannot be updated by the user at client deployment time and it is not automatically increased when the client is trying to mount a GPFS shared file system which has a block size larger than 1MB. As a result the GPFS client policy fails and the client instance goes into an error state if, at deployment time, it tries to mount a GPFS file system with a block size larger than 1MB. A GPFS file system with a block size larger than 1MB can be mounted by the client instance only after deployment. Before mounting the file system and creating the local link, the user should change the client cluster maxblocksize value by calling this command /usr/lpp/mmfs/bin/mmchconfig maxblocksize=<fileSystemBlockSize>
Local fix
Contact IBM Support
Problem summary
The code needed to be updated to accept a maximum block size parameter and process a maximum block size update operation.
Problem conclusion
A code fix is being provided in PureApplication System and BlueMix Local System version 2.2.3.0 in GPFS Pattern Type 1.2.8.0.
Temporary fix
Comments
APAR Information
APAR number
IT18456
Reported component name
PAPP SYS 8382 I
Reported component ID
5725G3200
Reported release
220
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-12-16
Closed date
2017-03-29
Last modified date
2017-03-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
PAPP SYS 8382 I
Fixed component ID
5725G3200
Applicable component levels
R223 PSY
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSM8NY","label":"PureApplication System"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.2.0.0"}]
Document Information
Modified date:
25 September 2021