This document describes the authorized program analysis reports (APARs) resolved in IBM Storage Scale 5.2.0.x releases.
This document was last updated on 6th June, 2024.
Tips:
APAR |
Severity |
Description |
Resolved in |
Feature Tags |
|---|---|---|---|---|
|
| |||
| IJ51056 | Suggested | When building the compatibility layer via mmbuildgpl with the -v option enabled warning messages from the compiler are reported. These messages can be ignored. The underlying source code is correct from a functional point of view. (show details) | 5.2.0.1 | Install/Upgrade Toolkit |
| IJ51011 | Suggested | Nessus vulnerability scanner found HSTS communication is not enforced on mmsysmon port 9980 (show details) | 5.2.0.1 | mmsysmon on GUI/pmcollector node |
| IJ50708 | Critical | In a file system with replication configured, the miss-update info set in the disk address could be overwritten by log recovery process, then lead to stale data to be read as well as the start disk process cannot repair such stale replicas. (show details) |
5.2.0.1 | Scale Users |
| IJ51036 | Medium Importance | mm{add|del}disk will fail which is triggered by signal 11. (show details) | 5.2.0.1 | disk configuration and region management |
| IJ51057 | Medium Importance | From a Windows client, in MMC permissions Tab on a share, the ACL listing was always showing as Everyone.If a subdirectory inside subdirectory is deleted, in the respective snapshot that was taken before, traversal to the inner subdirectory was showing errors. (show details) | 5.2.0.1 | SMB |
| IJ51037 | Suggested | mmkeyserv returns an error when used to delete a previously delete tenant, instead of returning a success return code. (show details) | 5.2.0.1 | File System Core |
| IJ51148 | High Importance | find or download all when run on a given path, sets timefor each of the individual entities with respect to COSand ends up blocking a following revalidation to fetchactual changes on the object's metadata from the COSto cache. (show details) | 5.2.0.1 | AFM |
| IJ51160 | Suggested | Daemon Assert gets triggered when afmLookupMapSize is set tohigher value of 32. Supported range is only 0 to 30. (show details) | 5.2.0.1 | AFM |
| IJ51222 | Suggested | If a problem with an encryption server happens just the Rkmid is visible in the default "mmhealth node show" view. Furthermore there are two monitoring mechanisms, one which will use an index to convey whether main or backup server is affected and one which will directly use the hostname or ip for that. Moreover the usual way to resolve an event with "mmhealth event resolve" has been broken for that component. (show details) | 5.2.0.1 | System Health |
| IJ51223 | Suggested | Customer are getting CES Failover in they dont use rsyslog. (show details) | 5.2.0.1 | CES |
| IJ51225 | High Importance | There is a build failure while executing mmbuildgpl command. The failure is seen while compiling /usr/lpp/mmfs/src/gpl-linux/kx.c due to no member named '__st_ino' in struct stat. Please refrain from upgrade to affected kernel and/or OpenShift levels until fix is available (show details) | 5.2.0.1 | Build / Installation |
| IJ51262 | High Importance | mmreclaimspace essfs1 --emergency-reclaim Pool 'system': failed to reclaim space (show details) | 5.2.0.1 | File system recovery |
| IJ51263 | High Importance | The size of the reserved emergency space is not always proper with the current reservation logic for the graceful emergency recovery. (show details) | 5.2.0.1 | File system recovery |
| IJ51264 | High Importance | Because 'thin-provisioning' is not fully enabled (i.e., space-reclamation only) for NVMe which include FCM drives, we can't set hasThinDisks in SGDesc for when FCM presents.The changes made to set hasThinDisks only when FCM not present. Note that the changes made inside of the StripeGroup::reserveThinSpaceForEachMount() function which is called only for SCSI when thin-provisioning attribute is appeared in the stanza file. For NVMe, the function is not called, except FCM... so that having the checking (of FCM presence) is good enough and will be safe. (show details) | 5.2.0.1 | File system recovery |
| IJ51265 | Critical | It is possible for EA overflow block to be corrupted as result of log recovery after node failure. This can lead to lost of some extended attributes that can not be stored in the inode. (show details) | 5.2.0.1 | All Scale Users |
| IJ50654 | High Importance | mmshutdown caused kernel crash while calling dentry_unlink_inode with the backtrace like this: ... #10 page_fault at ffffffff8d8012e4 #11 iput at ffffffff8cef25cc #12 dentry_unlink_inode at ffffffff8ceed5d6 #13 __dentry_kill at ffffffff8ceedb6f #14 dput at ffffffff8ceee480 #15 __fput at ffffffff8ced3bcd #16 ____fput at ffffffff8ced3d7e #17 task_work_run at ffffffff8ccbf41f #18 do_exit at ffffffff8cc9f69e ... (show details) |
5.2.0.1 | All Scale Users (Linux) |
| IJ51286 | High Importance | GPFS daemon could unexpectedly fail with signal 11 when mounting a file system if file system quiesce is triggered during the mount process. (show details) | 5.2.0.1 | All Scale Users |
| IJ51282 | High Importance | mmrestoreconfig also restores fileset configuration of a file systems. If the cluster version (minReleaseLevel) is below 5.1.3.0, the fileset restore will fail as it tries to restore the fileset permission inherit mode even if it is the default. The permission inherit mode was not enabled Storage Scale version 5.1.3.0. (show details) | 5.2.0.1 | Admin Commands SOBaR |
| IJ51283 | Suggested | Command mmchnode and mmumount did not cleanup tmp node files in /var/mmfs/tmp. (show details) | 5.2.0.1 | Admin Commands |
| IJ51287 | Suggested | Blank screen comes in black terminal background (show details) | 5.2.0.1 | CES-S3 |
| IJ51344 | Critical | When writing to a memory-mapped file, there is a chance that incorrect data could be written to the file before and after the targeted write range (show details) | 5.2.0.1 | All scale users |