IBM Storage Scale APARs Resolved in 5.2.3.x

Tips:

• To see the definition of the severity of an APAR in a tooltip, hover the cursor over the Severity column for that APAR.
• To search for a specific APAR, enter its ID in the Search APAR box at the top of the APAR column.
Show details for all APARs

APAR	Severity	Description	Resolved in	Feature Tags
IJ53815	High Importance	During or after upgrade of manager nodes to 5.2.0.0+, deadlock can occur. (show details) Symptom Cluster/File System Outage Environment All Operating System environments Trigger Manager node(s) are on version 5.2.0.0+. Client nodes are running a release prior to 5.1.9.0, or morethan one file system is under token migration at the same time. Workaround None	5.2.3.0	All Scale Users
IJ53828	High Importance	If the customer executes the systemops command, it will allow any command to be executed, as there is no specific command validation in place. (show details) Symptom None Environment Linux Only Trigger No such conditions Workaround None	5.2.3.0	No Such restriction
IJ54043	Medium Importance	When a file system maintenance command - mmrestripefs - or disk maintenance command - mm{ch,del,rpl}disk - run, the 'thin inode' is deallocated and the emergency space is deleted. This is unexpected behavior and could be a problematic if the file system gets OOS (Out-Of-Space) condition. (show details) Symptom After one of the commands run, the 'thin inode' in the internal dump will reset to -1 indicating that the 'thin inode' is deallocated and 'nBlocks' will be 0 indicating the emergency space is deleted. [root@c145f11san04b sju]# mmfsadm dump stripe | egrep "State of|thin inode" State of StripeGroup "test" at 0x18042A6A5B0, uid 7491A8C0:67D9B824, local id 1: 0: name 'system' Valid nDisks 32 nInUse 32 id 0 poolFlags 2 thin inode 41 nBlocks 519 1: name 'data' Valid nDisks 16 nInUse 16 id 65537 poolFlags 2 thin inode 42 nBlocks 526 2: name 'flash' Valid nDisks 8 nInUse 8 id 65538 poolFlags 2 thin inode 43 nBlocks 526 [root@c145f11san04b sju]# mmrestripefs test -R -N nc1 ... [root@c145f11san04b sju]# mmfsadm dump stripe | egrep "State of|thin inode "State of StripeGroup "test" at 0x18042A6A5B0, uid 7491A8C0:67D9B824, local id 1: 0: name 'system' Valid nDisks 32 nInUse 32 id 0 poolFlags 2 thin inode -1 nBlocks 0 1: name 'data' Valid nDisks 16 nInUse 16 id 65537 poolFlags 2 thin inode -1 nBlocks 0 2: name 'flash' Valid nDisks 8 nInUse 8 id 65538 poolFlags 2 thin inode -1 nBlocks 0 Environment Linux/AIX Trigger Run one of the command - mmrestripefs or mm{ch,del,rpl}disk Workaround None	5.2.3.0	thin-provisioning
IJ54044	High Importance	Because of the limitation in the current implementation in managing reserved inode pool, 'thin inode' can be shared erroneously with policy file while it is still assigned to the emergency space on the file system with SSS6K and FCM4 drives. This will trigger an 'assert' because of the corruption by being shared the same inode. And, it could also the file system metadata corruption by itself which will have consequence its own. (show details) Symptom After one of the commands run, the 'thin inode' in the internal dump will reset to -1 indicating that the 'thin inode' is deallocated and 'nBlocks' will be 0 indicating the emergency space is deleted. [root@c145f11san04b sju]# mmfsadm dump stripe | egrep "State of|thin inode "State of StripeGroup "test" at 0x18042A6A5B0, uid 7491A8C0:67D9B824, local id 1: 0: name 'system' Valid nDisks 32 nInUse 32 id 0 poolFlags 2 thin inode 41 nBlocks 519 1: name 'data' Valid nDisks 16 nInUse 16 id 65537 poolFlags 2 thin inode 42 nBlocks 526 2: name 'flash' Valid nDisks 8 nInUse 8 id 65538 poolFlags 2 thin inode 43 nBlocks 526 [root@c145f11san04b sju]# mmchpolicy test /home/sju/policy-default ... [root@c145f11san04b sju]# mmchmgr test c145f11san04a [root@c145f11san04b sju]# mmchpolicy test /home/sju/policy-default [root@c145f11san04b sju]# mmfsadm dump stripe | grep "policy file inode" policy file inode: 41 Environment Linux/AIX Trigger Run 'mmchpolicy' command multiple times. Workaround None	5.2.3.0	thin-provisioning
IJ54045	Medium Importance	To help controlling the issues (refer to D.341360, D.343470, and D.343471) with file systems created from SSS6K and FCM4, a new option 'thininode' is added to the tsdbfs command. This option will be used to reset 'thin inode'. (show details) Symptom With the command, 'thin inode' will be reset to the value as appeared in the tsdbfs command. [root@c145f11san04b sju]# mmfsadm dump stripe | egrep "State of|thin inode" State of StripeGroup "test" at 0x18042A6A5B0, uid 7491A8C0:67D9B824, local id 1: 0: name 'system' Valid nDisks 32 nInUse 32 id 0 poolFlags 2 thin inode 41 nBlocks 519 1: name 'data' Valid nDisks 16 nInUse 16 id 65537 poolFlags 2 thin inode 42 nBlocks 526 2: name 'flash' Valid nDisks 8 nInUse 8 id 65538 poolFlags 2 thin inode 43 nBlocks 526 [root@c145f11san04b sju]# tsdbfs test patch desc thininode 0 -1 [root@c145f11san04b sju]# tsdbfs test patch desc thininode 1 -1 [root@c145f11san04b sju]# tsdbfs test patch desc thininode 2 -1 [root@c145f11san04b sju]# mmfsadm dump stripe | egrep "State of|thin inode" State of StripeGroup "test" at 0x18042A6A5B0, uid 7491A8C0:67D9B824, local id 1: 0: name 'system' Valid nDisks 32 nInUse 32 id 0 poolFlags 2 thin inode -1 nBlocks 519 1: name 'data' Valid nDisks 16 nInUse 16 id 65537 poolFlags 2 thin inode -1 nBlocks 526 2: name 'flash' Valid nDisks 8 nInUse 8 id 65538 poolFlags 2 thin inode -1 nBlocks 526 Environment Linux/AIX Trigger Refer to D.343470 and D.343471 on the issues/symptoms and how to trigger. Workaround None	5.2.3.0	thin-provisioning
IJ54079	High Importance	An application using SMB server may invoke the gpfs_stat_x() call (available in libgpfs.so) to retrieve stat information for a file.Such call implements "statlite" semantics, meaning that the size information is not assured to be the latest. Other applications which invoke standard stat()/fstat() calls do expect the size information to be up to date.However, due a problem in the logic, after gpfs_stat_x() is invoked, information is cached inside the kernel, and the cache is not purged even when other nodes change the file size (for example by appending data to it). The result is that stat() invoked on the node may still retrieve out of date file size information as other nodes write into the file. (show details) Symptom Unexpected Results/Behavior Environment ALL Operating System environments Trigger SMB Applications invoking gpfs_stat_x() will cause wrong file size information to be retrieved by stat()/fstat() invoked by other applications. Workaround None	5.2.3.0	All Scale Users
IJ54328	Critical	Incorrect snapshot data—either stale or uninitialized—may be read while the mmchdisk start command is being executed on file systems with replication enabled. (show details) Symptom Data corruption, snapshot data read may not be as expected. Environment All platforms Trigger The issue may happen if some data replicas are stale or uninitialized, and snapshot data is accessed while  running the mmchdisk start command to repair the bad replicas. Workaround Avoid accessing snapshot data while running the mmchdisk start command.	5.2.3.0	GPFS core