| 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)
| Symptom |
Error output/message |
| Environment |
ALL Linux OS environments |
| Trigger |
Executing mmbuildgpl with the -v option enabled for building compatibility layer. |
| Workaround |
No work around available. |
|
5.2.0.1 |
Install/Upgrade Toolkit |
| IJ51011 |
Suggested |
Nessus vulnerability scanner found HSTS communication is not enforced on mmsysmon port 9980
(show details)
| Symptom |
Nessus vulnerability scan finding/record (medium severity) |
| Environment |
Linux |
| Trigger |
Nessus vulnerability scan |
| Workaround |
None |
|
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)
| Symptom |
replica mismatch |
| Environment |
All Operating Systems |
| Trigger |
I/O errors happening and generating miss-update info into the disk address of data blocks, and then a mmfsd daemon crash could result in such problem. |
| Workaround |
None |
|
5.2.0.1 |
Scale Users |
| IJ51036 |
Medium Importance |
mm{add|del}disk will fail which is triggered by signal 11.
(show details)
| Symptom |
failure of the command. |
| Environment |
Linux Only |
| Trigger |
Run mm{add|del}disk with multiple NSDs. |
| Workaround |
The problem/symptom would typically occur when there are multiple NSDs added/deleted with the command. By running
the command with one NSD at a time, we can avoid the problem/symptom. |
|
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)
| Symptom |
Error output/message |
| Environment |
ALL Operating System environments |
| Trigger |
The MMC permissions problem can happen in case of viewing permissions from MMC permissions tab for a share. Snapshot traversal would show problems from client when a sub-directory within sub-directory is deleted on the actual filesystem and the same is tried for access in snapshot directory. |
| Workaround |
None |
|
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)
| Symptom |
Failure to remove an already deleted tenant. |
| Environment |
ALL Linux OS environments |
| Trigger |
Remove a Scale tenant from the GKLM server prior to invoking the 'mmkeyserv tenant delete' command. |
| Workaround |
mmkeyserv can be used with the --force option to remove the Scale definition of a deleted tenant. |
|
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)
| Symptom |
Unexpected Behaviour |
| Environment |
All OS Environments |
| Trigger |
Performing an ls on directory before trying lookup for the file. |
| Workaround |
None |
|
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)
| Symptom |
Abend/Crash |
| Environment |
All OS environments |
| Trigger |
Setting value of afmLookupMapSize to high value of 32. |
| Workaround |
set the value of afmLookupMapSize in the 0 to 30 range only. |
|
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)
| Symptom |
Unexpected Results/Behavior |
| Environment |
ALL Linux OS environments |
| Trigger |
Code change to have RkmId as the common ground for old and new monitoring methods. |
| Workaround |
mmhealth node show encryption -v (or -Y) to see the server information. mmhealth node eventlog -Y would work as well. Resolving the event needs a "mmsysmoncontrol restart" |
|
5.2.0.1 |
System Health |
| IJ51223 |
Suggested |
Customer are getting CES Failover in they dont use rsyslog.
(show details)
| Symptom |
Performance Impact/Degradation |
| Environment |
Linux Only |
| Trigger |
rsyslog should have inactive/not installed |
| Workaround |
None |
|
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)
| Symptom |
Build failure while building kernel gpl modules. |
| Environment |
Linux Only
OpenShift 4.13.42+, 4.14.14.25+, 4.15.13+ with IBM Storage Scale Container Native, Fusion with GDP |
| Trigger |
The problem could be triggered by newer kernels containing Linux kernel commit 5ae2702d7c482edbf002499e23a2e22ac4047af1 |
| Workaround |
None |
|
5.2.0.1 |
Build / Installation |
| IJ51262 |
High Importance
|
mmreclaimspace essfs1 --emergency-reclaim Pool 'system': failed to reclaim space
(show details)
| Symptom |
E_IO returned causing the command failure. |
| Environment |
Linux Only |
| Trigger |
Run 'mmreclaimspace <fs> --emergency-reclaim. |
| Workaround |
None |
|
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)
| Symptom |
None |
| Environment |
Linux Only |
| Trigger |
Follow the steps in the graceful emergency recovery. |
| Workaround |
None |
|
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)
| Symptom |
None |
| Environment |
Linux Only |
| Trigger |
Follow the steps in the graceful emergency recovery. |
| Workaround |
None |
|
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)
| Symptom |
Operation failure due to FS corruption |
| Environment |
ALL Operating System environments |
| Trigger |
Node failure after repeated extended attributes operations which trigger creation and deletion of overflow block |
| Workaround |
None |
|
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)
| Symptom |
Kernel crash during mmshutdown |
| Environment |
All Linux OS environments |
| Trigger |
Kernel crash with dentry_unlink_inode when run mmshutdown.For the normal open(), the kernel seems to call fops_get, which is a call totry_module_get.
The fix: We need to call try_module_get when we install cleanupFD. This will hold the module in place until gpfs_f_cleanup (called when the lastmmfsd process terminates and allows basic cleanup for next daemon startup) has been called for the cleanupFD. |
| Workaround |
None |
|
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)
| Symptom |
Abend/Crash |
| Environment |
ALL Operating System environments |
| Trigger |
File system quiesce triggered via file system command while file system mount is in progress |
| Workaround |
Avoid running commands that trigger file system quiesce while client nodes are in the process of mounting the file system |
|
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)
| Symptom |
• Error output/message
• Unexpected Results/Behavior |
| Environment |
ALL Linux OS environments |
| Trigger |
mmbackupconfig and mmrestoreconfig on Storage Scale Product version 5.1.3.0 or higher while the cluster minReleaseLevel is below 5.1.3.0. |
| Workaround |
N/A |
|
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)
| Symptom |
Unexpected Results/Behavior |
| Environment |
ALL Operating System environments |
| Trigger |
Run mmchnode and mmumount command. |
| Workaround |
Manually remove leftover tmp files from mmchnode and mmumount |
|
5.2.0.1 |
Admin Commands |
| IJ51287 |
Suggested |
Blank screen comes in black terminal background
(show details)
| Symptom |
Abend/Crash |
| Environment |
Linux Only |
| Trigger |
execute the mms3, it can come if mms3 command gives any warning message |
| Workaround |
Change black background to any other color
|
|
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)
| Symptom |
Unexpected Results/Behavior |
| Environment |
ALL Operating System environments |
| Trigger |
Writing to memory-mapped files with offsets and lengths unaligned to the internal buffer range size (usually subblock size or 4k) could cause incorrect data to be written before and after the targeted write range |
| Workaround |
Stop using memory-mapping |
|
5.2.0.1 |
All scale users |