Unless specifically noted otherwise, this history of problems fixed for GPFS 4.1.x applies for all supported platforms.
Problems fixed in GPFS 4.1.0.1 [June 06, 2014]
- Fix thread-safe problem in dumping GPFS daemon threads backtrace.
- Fixes a problem with fsck repair of deleted root directory inode of independent filesets.
- Fixed a problem in clusters configured for secure communications (cipherListconfiguration variable containing a cipher other than AUTHONLY) which may cause communications between nodes to become blocked.
- After a file system is panicked, new lock range request will notbe accepted.
- This fix only affects customers running GNR/GSS on Linux, and who have in the past misconfigured their GNR servers by turning the config parameter "numaMemoryInterleave" off, and who experienced IO errors on Vdisks as a result of that misconfiguration. These IO errors can potentially corrupt in-memory metadata of the GNR/GSS server, which can lead to data loss later on. This fix provides a tool that can be used to locate and repair such corruption.
- Remove mmchconfig -N restrictions for aioWorkerThreads and enableLinuxReplicatedAio.
- Fixed problem when reading a clonde child from a snapshot
- Fixed a rare race condition causing the assert when two threads are attempting to do a metanode operation at the same time whilethe node is in the process of becoming a metanode.
- Fixed a deadlock in a complicated scenario involving restripe,token revoke and exceeding file cache limit.
- Fixed race between log recovery and mnodeResign thread
- E_VALIDATE errors in the aclFile after node failure
- Deal with stress condition where mmfsd was running out of threads
- Fix a problem in log recovery that would cause it to fail when replaying a directory insert record. The error only occurs for filesystems in version 4.1 format, where the hash value of the file name being inserted is the same as an existing file in the directory. The problem is also dependent on the length of the file name, and only happens if the system crashes after the log record is committed, but before the directory contents are flushed.
- Fixed the problem that was caused by a hole in the cleanBufferafter the file system panicked.
- Close a hole that fileset snapshot restore tool (mmrestorefs -j) may cannot restore changed data for a clone child file.
- Fix a rare assert which happens under low disk space situation
- Fixed deadlock during mmap pagein
- Fixed the problem of excessive RPCs to get indirect blocks and the problemof metanode lock starvation involving a huge sized sparse file.
- A problem has been fixed where the GPFS daemon terminates abnormallywhen direct I/O and vector I/O (readv/writev) is used on encrypted files,and the data is replicated, or the data must go through an NSD server.
- Fix a potential deadlock when selinux is enabled and FS is dmapi managed.
- Close a hole that fileset snapshot restore tool (mmrestorefs -j) may cannot restore a snapshot in a race condition that one restore thread is deleting a file but another restore thread is also trying to get file attributes for this file.
- Fixed a kernel oops that caused by a race in multiple NFS readson the same large file.
- mmchfirmware command will avoid accessing non-existent disk path.
- Fix a directory generation mismatch problem in an encrypted secvm file system.
- shutdown hangs in the kernel trying to acquire revokeLock
- Apply at your convenience. Even if you hit this bug, an equivalent cleanup is completed later in the command execution.
- improved stability of daemon-to-daemon communications when cipherList is set to a real cipher (i.e. not AUTHONLY).
- The serial number of physical disks is now recorded in the GNR event log, and displayed in the mmlspdisk command.
- GNR on AIX allow only 32K segment.
- Fixes a problem with fsck repair of corrupt root directory inode
- mmbackup tricked by false TSM success messages Mmbackup can be fooled by TSM
output when dsmc decides to roll-back a transaction of multiple files being
backed up. When the TSM server runs out of data storage space, the current
transaction which may hold many files will be rolled back and re-tried with
each file separately. The failure of a file to be backed up in this case was
not detected because the earlier message from dsmc contained "Normal File -->
[Sent]" though it was later rolled back. Fixes in tsbuhelper now detect the failure signature "** Unsuccessfull **" string and instead of simply ignoring these now will revert the changes in the shadow DB for the matching record(s). Hash table keeps track of last change in each record already, so reverting is now a legal state transition for hashed records. Reorganized some debug messages and streamlined some common code to work better. Now find 'failed' string to issue reversion updates as well. Fixed pattern matching in tsbackup33.pl to properly display all "ANS####" messages. - Fix RO cache i/o error if mounting fs in ro mode.
- Don't release mutex if daemon death.
- Fix the path buffer length calculation to return the correct length for dm_handle_to_path() functions.
- Fix bug in mmauth that may cause duplicate configure entries and node numbermismatch in configure file.
- Fix a problem with creating directory if the parent directory has default POSIX ACL.
- mmbackup fails to read hex env values mmbackup debug values, progress reporting, and possibly other user settings may be presented in decimal or hex, especially the bit-mapped progress and debugging settings. Perl doesn't always interpret the hex values correctly unless converted with the oct() function.
- Correct an NLS-related problem with mmchdisk and similar commands.
- This update addresses the following APARs: IV60187 IV60468 IV60469 IV60471 IV60475 IV60478 IV60543 IV60863 IV60864.