Readme and Release notes for release 4.2.2.1 IBM Spectrum Scale 4.2.2.1 Spectrum_Scale_Express-4.2.2.1-x86_64-Windows Readme

Unless specifically noted otherwise, this history of problems fixed for IBM Spectrum Scale 4.2.x applies for all supported platforms.

Problems fixed in IBM Spectrum Scale 4.2.2.1 [December 16, 2016]

• CNFS: fix recursive calls during shutdown which may cause LOGASSERT.
• Fix data corruption that can occur writing large files using parallel IO and multiple gateway nodes.
• Fix a kernel crash during mmshutdown in kxAttachSharedMemory by tsctl process.
• Fix "mutexMagic != 0x59C0DEAD" assert by the SGExceptionLocalPanicThread that can occur during quorum loss.
• mmlsfileset: allow remote file system. Option -i and -d are now allow.
• mmstartup: verify kernel/module configuration before start runmmfs.
• Fix a very rare race condition that can lead to kernel panic. This issue could only occur on Linux when a mix of AIO and buffered IO are being used to read and write to the same file from multiple nodes.
• Fix data mismatch problems and snapshot mismatches between old primary and acting primary during an applyUpdates in the failbackToPrimary procedure.
• Fix a problem in which mmbackup returns the wrong number of objects handled. This can occur if NUMBERFORMAT is set incorrectly.
• Fix Kernel BUG: illegal operation locks_wake_up_blocks+0x6c.
• mmlsconfig: may not return correct value due to stale cache.
• Fix code to prevent a possible kernel panic during GPFS daemon shutdown on Linux. In order for problem to occur, filesystem must be mounted with active workload when GPFS daemon is been shutdown.* Fix assert in the Gpfs daemon by disallowing GetAttr for DR Primary fileset.
• Fix assert in the daemon that can occur during a Gateway queue transfer and new gateway node joins at the same time.
• Fix slow offline fsck repair. Allow doDeferredDeletions() to cleanup afm pre-destroyed inodes in ex-afm filesets.
• Fix a deadlock that can occur if a node of the cluster is down while GPFS attempts to establish a RDMA connection using RDMA CM.
• Fix an issue in AFM environment where queue memory usage threshold (afmHardMemThreshold) is not honored.
• Fix a remote error 17 creating and deleting hardlinks to files during log recovery.
• Fix a mmsdrrestore command failure that can occur when a tiebreaker disk is in use (CCR setup).
• This fix will make sure data is synced to disk only when required.
• Fix mmfsd crash in an AFM environment that can occur when a lookup on the same file is triggered from multiple nodes.
• Fix a debug assert in performPcacheMsg that can occur when the hardQMemLimit is hit for a fileset.
• During IFS System upgrade, occasionally node crash is observed if AFM is configured and in use.
• Fix Renames clogging the AFM queue during recovery for IW filesets.
• Apply this fix if you are troubled by bogus messages in the mmfs log files during file system creation.
• This modification does not change the functionality of GPFS, neither affects the appearance of the software, however it improves the effectiveness (speed) of the code in certain disk operations and introduces a mechanism (by explicitly distinguishing user- and kernel-space objects) that can be used for implementing other critical parts on s390x platform.
• Fix a deadlock that can occur during high volume file creations and deletions in a multi cluster environment.
• Fix mmlsquota -j returning a wrong answer that can occur if there is a special character in the name of the stripe group.
• Handle upgrade of Windows node from 3.5 and 4.1 to 4.2 correctly.
• Fix a problem in which mmces fails to change the address of object protocol attributes.
• Honor parent folder's DELETE_CHILD right during rename operation from Windows node.
• Fix a problem in which mmbackup with -B value > 32768 causes missed files.
• Applications using dmapi for HSM may benefit by knowing if a file that is being migrated is currently open and being accessed on some node in the cluster. Extend the dmapi dm_get_fileattr command to take a new flag "DM_AT_FOPEN" to query if the file is open anywhere in the cluster.
• Prevent the execution of mmhealth on unsupported nodes.
• Change in dmapi dm_stat_t structure returned by dm_get_fileattr used by TCT. Update must be coordinated with TCT update.
• This update addresses the following APARs: IV90831 IV90833 IV90864 IV90865 IV90869 IV90874 IV90878 IV90880 IV90891 IV90892 IV91054 IV91144 IV91145 IV91327 IV91443.