GPFS v3.3.0.3 now available
Announcing the availability of the service level 3.3.0.3 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.
* On x86_64 Linux when special encoding flag is set in a functions debugging frame section, an extra offset should be added during decoding. Otherwise, the thread traceback can not be decoded correctly.
* Fix Stripe group configuration change so data block loss cannot occur if data is being ingested along with configuration changes.
* On Windows, consolidated separate -msi and -sh installation logs into a single file(gpfs-install.2009.10.20.11.23.58.gpfs-n70-win.log). Also, eliminated Command window popups that were appearing during GPFS installation.
* Fix problem where the new inode scan function gpfs_next_inode64() would return incorrect values for some gpfs_iattr64_t fields on file systems originally created prior to GPFS 2.3.
* Change to GPFS inode scan api for gpfs_ireaddir64. Directory entry structure returned by call now contains a flag field and allows directory entry names to be 1020 bytes (ie 255 characters encoded in UTF-16 or other Unicode encodings).
* Fix policy handling of rules of the form “EXCLUDE FROM POOL” to prevent LOW_SPACE events from incorrectly being logged.
* Extended Attributes (EAs) on Windows have been changed so that internally they are stored with a “user.” prefix. This change supports compatibility with Linux and improves file system security.
* Fix problem on systems configured with large maxFilesToCache that could cause file systems to be unmounted on some client nodes when running recovery after a manager node failure.
* Fixed GPFS hang when recalling files from HSM.
* When running lsvg do not wait for the volume group lock.
* Fix mmbackup to give users early warning and exit when unlinked filesets are present during backup. It also prevents further processing of files that would otherwise give the user misleading error information.
* Limit the number of attempts made to destroy nfsd threads in mmnfsquorumloss in case an nfsd thread is stuck waiting for IO to complete in GPFS.
* Don’t stop NFS or unexport fs on quorum loss, and kill NFSDs that are stuck during setNfsdProcs.
* Fix mmdelnode syntax error checking.
* Fixed the allocation code which caused a loop during metadata allocation. This problem only affects filesystem with metadata replication enabled.
* Fix mmbackup incremental to handle conversion from short filename records to new longer records after upgrade to 3.2.1.14 or later.
* Fix Linux “mmnfsinit start” command and return correct return code.
* Fix problem where a multi-threaded workload reading extended attributes from a large number of files could cause accumulation of a large number of byte range tokens leading to slowdown and spurious ENOMEM errors.
* Upon mmfsd daemon failure, change the way of debug data collection to asynchronous script execution.
* Fix a quota initialization problem that could allow quota files in storage pools, while they really belong in system pool.
* Fix for a rare race condition that may cause an assert in the invalid fileset object disposal path.
* Added new command line option “–oneerror” to mmaddcallabck command.
* Enable mmapplypolicy on fs with 8MB blocksize.
* Correct processing to prevent quota requests from being performed while the quota manager operations are being quiesced.
* Converted GPFS to use the Windows sockets library (WinSock) rather than the SUA library. This change fixed an issue with large data transfers that appeared when a file system’s block sizes was larger than 256KB. The WinSock library also significantly reduces the CPU consumption required to perform network data transfers.
* Fixed error handling when registering pagepool memory to Infiniband.
* Correct quota hard limit processing to check grace time.
* Correct a rare problem (due to an error encountered writing quota files) that can prevent a newly created filesystem from being mounted.
* Improve stability when encountering hostname resolve issues.
* Prevent callback command path in GPFS file system.
* Fixed a problem which prevents filesystem remount after a forced umount due to error(ie. filesystem panic,quorum loss, etc).
* Fix panic handler code to ensure that the right fsck cleanup code path is chosen by looking at the workerNode flag in the fsck data structure.
* Correct processing during restoring filesets to allow more than the KSH array limit of 1024.
* Fix quota manager cleanup when file system manager migrates to another node.
* Fix a file structure error caused by SetAllocationSize.
* Enable kdump to retrieve kernel thread’s backtrace on IA64.
* Handle IB port event of LID change.
* Correct a problem when verifying that the daemon is down from a Windows node.
* Resolved an issue with mmwinservctl where the command would fail to set the account name and password. This error would occur if Windows is not installed in same location on all nodes in the cluster (e.g. some nodes have Windows installed on the C: drive and other have it installed on the D: drive.)
* Fix to avoid assertion when calculating the next valid data block number of low level file.
* Removed some commands and programs that were included in the Windows installation, but not supported on Windows.
* Parse the ‘ro’ mount option and pass it explicitly to gpfsMount to prevent Windows write on readonly filesystem.
* Fix mmbackupconfig in Windows to give the customers the correct mmbackupconfig behavior and exit gracefully.
* Fix mmapplypolicy to run on a large number of files with the -g and -N flags.
* Make filesystem restore messages for mmrestoreconfig more descriptive.
* Fix mmbackup to backup snapshots that are older than the latest filesystem backup.
* Fix mmbackup to ensure that the only desired TSM servers will be processed.
* Package mmbackup32 for use with 3.2 clients.
* Add support for -N nodeList option in mmbackup version 3.1 and 3.2.
* Fix possible deadlock restriping a file system with data replication enabled under application load and with small pagepool.
* Warning messages on conflicting opertaions are sent to stderr to avoid littering to stdout.
* Resolved an issue that in rare cases could cause GPFS to terminate when tracing is enabled.
* Fixed some mmwinservctl operations which were causing GPFS to start inadvertently when GPFS was configured with autoload=yes.
* Fix mmchconfig trace command to load kernel extensions if not already loaded.
* Increase the default maximum size of the shared segment on 64-bit AIX to 1G (32-bit AIX is architecturally limited to 256M).
* This update addresses the following APARs: IZ63333 IZ65179 IZ65379 IZ65416
« IBM Power Systems Announcement Overview Oct 09 | Home | Trusted AIX – Call us to secure your AIX platform today! »
Leave a Comment