Unless specifically noted otherwise, this history of problems fixed for IBM Spectrum Scale 4.2.x applies for all supported platforms.
Problems fixed in GPFS 4.2.3.1 [May 16, 2017]
- Fix a Ganesha crash caused by an applyUpdate.
- Fix a ccrio initialization failure (err 811) when changing the daemon-interface.
- Fix a rare segmentation fault in the mmgetstatus command.
- Fix a SIGBUS error that can occur during a mmap read on a snapshot file.
- Fix a problem in which we see a flood of "failed to scrub vdisk" log message when GNR node experiences quorum loss. This is for ESS/GSS.
- Fix a rare race between unlink, lookup and token revoke which causes kernel crash in d_revalidate.
- This fix will make sure Ganesha request reference a valid GPFS filesystem.
- Fix a system hang that can occur when a file system is suspended while doing a mmap.
- This fix rejects unreasonable large requests to preallocate inodes immediately with ENOSPC.
- Fix a directory rename issue with IW filesets that can occur if the rename target is an existing directory.
- Fix a fault that can occur when restripe runs while the SG is not mounted on all NSD nodes.
- This fix restricts the afmMaxParallelRecoveries config value from 0 to 128.
- This fix removes the unnecessary error message "cannot open /proc/net/tcp6" when shutting down GPFS.
- Fix a problem with not properly handling quotas in an AFM environment. This can occur when you have very large hard and soft limit values.
- Fix a "exp(!sgP->isSGMgr())" assert that can occur when you delete a file system and then create a new file system with the same name at the same time.
- Fix an err 112 that can show up in the mmfs logs when mmchnode --gateway is executed.
- Fix a kernel crash that can occur while attempting to mount a loop device to a correspond file in a GPFS file system or while using a GPFS file system file as a LIO backend.
- Address a problem where applyUpdates continues to run even if the fileset at the old primary is unlinked or the mmfs daemon has been shutdown.
- Fix an outband resync failure that can occur if a recovery is triggered by deleting some files in a directory and the directory itself. This is an AFM/DR environment.
- Fix rename conflicts that can occur in SW/DR filesets.
- Update log code to prevent log recovery error when log file became illReplicated. This could happen on file system with -K set to NO and there is not enough disk space for full replication.
- This fix will use new interface that will reduce multiple retries every time a lock is freed and there are multiple waiters for the lock.
- Fix an assert that can occur with a DR fileset and the file system is suspended.
- Fix bug that requires a large free space in /var/mmfs to run change commands.
- Fix recovery failure err 17 when psnap0 deletion fails.
- Fix a daemon assert that can occur in an AFM environment where the mmfsd daemon fails to start repeatedly with a DMAPI enabled filesystem at a gateway node.
- Address a problem where trying to queue a writeSplit message to the helper gateway's queue can fail with an error 28 (E_NOSPAC).
- Fix an issue which returns EACCESS(errno = 13) while running mmapplypolicy when there is a mounted NFS file system which has the same name with a GPFS file system.
- A fastpath optimization defect can result in an internal error to be returned to the user when it is safe to continue without entering the fast path.
- Install if you suffer from mmapplypolicy/tspolicy hanging after otherwise finishing all work.
- cNFS: fix a problem with /usr/sbin/rpcinfo not found in SLES12 or later.
- Fix a failure in Object Authentication configuration with Active Directory or LDAP. This fix is only required if Object is being configured with Active Directory or LDAP and DN of Swift service user(specified in --ks-swift-user) is more than 79 characters.
- Fix a problem with ESS disk replacement in which the mmchcarrier command may wipe out the pdisk location code. The problem will prevent the subsequent mmchcarrier command to proceed without a valid location code.
- Fix a problem in which a GPFS command may wrongly terminate another process.
- Fix a rare deadlock problem caused by stream write(enableRepWriteStream=yes).
- Update log recovery code to avoid GPFS daemon assert after detecting invalid directory block during log recovery. Code has been changed to log a FSSTRUCT error and fail the log recovery so offline mmfsck can be run on the file system.
- Fix a mmfsd crashes (incompleteOk assertion), when the number of files in the committed directory doesn't match the number of files in CCR's file list in case of a new CCR file update request.
- This update addresses the following APARs: IV94991 IV94992 IV94994 IV94995 IV94996 IV94997 IV94998 IV95015 IV95021 IV95230 IV95557 IV95643 IV95925 IV96037 IV96163.