GPFS V3.3.0.4 now available
Announcing the availability of the service level 3.3.0-4 for all GPFS V3.3 products.
The service level is available at: GPFS download site
This service level addresses the below issues. This is not a definitive list as other minor corrections have been made which are not listed here.
* Fix problem where mmrestripe command might not correctly detect I/O errors during the first phase of restripe.
* Correct the resetting of config parameters to default on a subset of the nodes.
* Replace usage of the lsvg command with getlvodm.
* Fix function checkIntRange error message when checking negative numbers.
* Clear the tiebreaker disk parameter after mmexportfs all.
* Fix ioctl opcode conflict with FIGETBSZ on Linux kernel 2.6.31 and later.
* Fix fsck to avoid incorrectly reporting and fixing of filesystem corruptions in a heterogeneous cluster.
* If the file system is internally forced to unmount (file system panic), invoke the preunmount user exit if one is installed.
* Avoid confusion when using a local fcntl lock versus an NLM one.
* Give customers using mmbackup more flexibility by allowing alternate install location for TSM.
* Fix determining filename length when filename contains invalid UTF8 characters.
* Fix data corruption when using mmap.
* Fix assert due to invalid fcntl acquire sleep element found on the kernel queue.
* Keep FS descriptors off of excluded disks even if they come online.
* Fixed a race condition by serializing the xattr object in inode properly.
* Fix hang between node failure thread and events exporter request handler thread.
* Fix mmapplypolicy to estimate correctly the number of GPFS storage pool bytes freed by migrating to an external/HSM pool. Introduce MM_POLICY_MIGRATION_STUBSIZE environment variable to allow users to directly control size for migration.
* Fix mmbackup to avoid giving file name length and file size to TSM for inclusion in backup list.
* Fix async recovery to let mounts succeed while also processing deffered deletions.
* Fix assert failure on FS manager node when unmountOnDiskFailure=yes and a disk fails after 3.2.1.14-16 installed.
* Prevent HSM and NFS from asking to open inodes that are system metadata nodes.
* Don’t let socket get stuck in reconn_cleanup state following repeated breaks that occur just after connection handshake completes.
* Reduce the pagepool usage by inode allocation segments during FS manager initialization or recovery.
* Fix a problem with cutting traces in a CNFS setup.
* Fix filesystem panic when a failed disk holds a FS descriptor and returns unexpected error codes.
* Fix problem with mmlsfileset when expanding inodes is running concurrently.
* Ignore un-supported permission flags passed to gpfs_i_permission on SLES11.
* Fix for a SIGSEGV on Windows caused by a race in accessing the ACL file.
* Fix a condition where mm commands can exit with errors if CWD is unavailable.
* Fix for a rare failed assert in the main process thread on Linux.
* Fix a race condition where node may be deleted right after it started up.
* Fix code to correct backward compatibility of non-blocking token request between gpfs 3.2 and gpfs 3.3.
* Make trace recycle timeout message more descriptive and avoid recycle file being overwritten when trace recycles next time (Linux nodes only).
* Succedent tscrfs command will unset some flags unexpectedly even if it cannot get the permission to run. It will cause a daemon assert. Clear flags only if the command has set it before.
* When open of the directory fails and not all fields are set, don’t call back into GPFS to do close (release). This may cause an invalid assert due to attempting to reference uninitialized fields.
* Fix signal 11 due to bad RDMA index and cookie received from the TcpConn in verbs::verbsClient_i.
* Fix remote startup on Windows.
* Fix a race condition between an mmexpelnode and mmchmgr.
* Correctly cleanup tmp files on remote nodes.
* Fix a problem in mmdf where number of free inodes may become negative.
* Fix race condition that occurs due to disk failure during clmgr election while using tiebreaker disks.
* Fixed inode expansion code which can cause restripe to fail with an assert. This problem only happens when restripe and inode expansion run concurrently.
* Several sample script and configuration files are now included with the GPFS for Windows installation. These can be found in %SystemRoot%\SUA\usr\lpp\mmfs\samples. Only the files appropriate for use on Windows are included; additional samples are available with UNIX installations.
* Fix assert “offset < ddbP->mappedLen” when reading dirs.
* Fix allocation manager problem that caused pool to not be deleted when it should have been.
* Initialize allocSize variable during the initialization phase of file repair to prevent assert.
* Fix a rare bug that occurs during nsd config change along with earlier disk issues to another deleted nsd.
* Fixed a GPFS on Windows failure that can occur on systems with a large number of cores (e.g. 8 or more) running a workload with thousands of threads. When this error occurs, /var/adm/ras/mmfs.log.* shows “logAssertFailed: tid >= 0 && tid <= MAX_GPFS_KERNEL_TID”. The fix for this problem removes any assumption on the maximum thread ID.
* Fix a problem that can lead to loss of an intermediate SSL key file.
* Fix mmbackup to accurately reflect the error encountered on the TSM server.
* Fix a problem with interpreting the syncnfs mount option.
* Fix fsck so that it reports duplicate fragments and its count correctly and also prevent a possible fsck crash due to count overflow.
* Added %myNode as callback parameters.
* Fix an assertion during mount that could happen when quota management is enabled and snapshot is being used.
* Fix fsck so that it detects problems and fixes them without encountering struct assert errors even if the ‘assertOnStructureError’ config option is turned on.
* This update addresses the following APARs: IZ67659 IZ67660 IZ67661 IZ67662 IZ67663 IZ67664 IZ67665 IZ67666 IZ67667 IZ67723 IZ67746 IZ68028.
Doc number: 4931 Published date: 20100130
« Spectrum passes another 2 IBM Power Certifications | Home | Student Feedback from IBM Training »
Comments are closed.