IC SunsetThe developerWorks Connections Platform is now in read-only mode and content is only available for viewing. No new wiki pages, posts, or messages may be added. Please see our FAQ for more information. The developerWorks Connections platform will officially shut down on March 31, 2020 and content will no longer be available. More details available on our FAQ. (Read in Japanese.)
Topic
  • 39 replies
  • Latest Post - ‏2019-04-26T16:30:41Z by gpfs@us.ibm.com
gpfs@us.ibm.com
gpfs@us.ibm.com
662 Posts

Pinned topic IBM Spectrum Scale V4.2.2 announcements

‏2016-12-21T01:59:19Z |

GPFS 4.2.2.1 is now available from IBM Fix Central:

http://www-933.ibm.com/support/fixcentral

Problems fixed in GPFS 4.2.2.1

December 20, 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.

Updated on 2016-12-21T02:00:17Z at 2016-12-21T02:00:17Z by gpfs@us.ibm.com
  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-02-23T15:42:12Z  

    Flash (Alert) IBM Spectrum Scale V4.2.1/4.2.2 parallel log recovery function may result in undetected data corruption

    Abstract

    IBM has identified a problem with the IBM Spectrum Scale parallel log recovery function in V4.2.1/V4.2.2, which may result in undetected data corruption during the course of a file system recovery.

     

    See the complete Flash at http://www-01.ibm.com/support/docview.wss?uid=ssg1S1009965

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-03-07T15:58:37Z  

    Technote:  IBM Spectrum Scale Support: SKLM 2.7 UUID Length Workaround and Fix

    Problem(Abstract)

    IBM Spectrum Scale versions up to and including 4.2.2.2 (and ESS versions up to and including ESS 5.0.0) only support master encryption keys with identifiers up to 42 characters in length. With V2.7, IBM Security Key Lifecycle Manager (SKLM) generates encryption keys which are by default up to 48 characters long. Therefore, such keys cannot be used for encryption by Spectrum Scale.

    See the complete Technote at  http://www.ibm.com/support/docview.wss?uid=ssg1S1010026

    Updated on 2017-04-27T20:02:27Z at 2017-04-27T20:02:27Z by gpfs@us.ibm.com
  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-03-29T17:42:38Z  

    Technote:  IBM Spectrum Scale support:  Kernel crashes on Ubuntu 16.04.1 with kernel version 4.4.0-57 or later

    Problem (Abstract)

    When using Ubuntu 16.04.1 and upgrading the kernel version to 4.4.0-57 or later, you may encounter a kernel crash issue when there are some operations involving setting and removing an extended file attribute, e.g. using the setxattr and removexattr syscall.

     

    See the complete technote at :  http://www.ibm.com/support/docview.wss?uid=ssg1S1010071

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-04-08T14:35:02Z  

    Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Spectrum Scale

    Summary

    There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition, Version 8 used by IBM Spectrum Scale. These issues were disclosed as part of the IBM Java SDK updates in Jan 2017.


    See the complete bulletin at http://www-01.ibm.com/support/docview.wss?uid=ssg1S1010033

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-05-09T22:12:32Z  

    Flash (Alert) IBM Spectrum Scale:  O_SYNC/O_DSYNC not honored, potentially causing some writes to be lost

    Abstract

    IBM has identified a problem with IBM Spectrum Scale V4.2.0.1 through V4.2.2.3, in which the  O_SYNC/O_DSYNC flag to the open() system call could be ignored, which may result in undetected data corruption due to writes to the file (which appear to have been completed) being lost if a node failure occurs before data is written to disk.

    See the complete Flash at:  http://www.ibm.com/support/docview.wss?uid=ssg1S1010130

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-05-30T21:58:51Z  

    Flash (Alert): IBM Spectrum Scale (GPFS): Asynchronous I/O write: file size change may not be updated

    Abstract

    IBM has identified an issue with IBM Spectrum Scale V4.1.0.4 through V4.1.1.14 and V4.2.0.0 through V4.2.3.0 levels when asynchronous Direct I/O is used to write to a file on LINUX, using the io_submit interface.

    Problem Summary:

    As a result of an asynchronous Direct I/O write using the io_ submit interface, file size change may not be updated correctly, leading to possible undetected loss of data when a node fails before file size change is committed to disk.

     

    See the complete Flash at: http://www-01.ibm.com/support/docview.wss?uid=ssg1S1010223

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-06-30T15:49:52Z  

    Flash (Alert): IBM Spectrum Scale (GPFS): On I/O with file size change on metanode takeover, the file size change may not be committed to disk

    Abstract

    IBM has identified an issue with IBM GPFS and IBM Spectrum Scale versions when a file size change that happens during a small timing window at the non-metanode may not be committed to the disk during metanode takeover.

    Problem Summary:

    A very small timing window exists in which a file size change, resulting from an append that happens on a non-metanode, may not be committed to the disk when that node takes over as metanode, leading to possible undetected data loss.  If the data involved uses GPFS encryption (IBM GPFS 4.1.x or later), this may also result in undetected data corruption. 

    See the complete Flash at:  http://www.ibm.com/support/docview.wss?uid=ssg1S1010293

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-06-30T15:52:12Z  

    Flash (Alert): IBM Spectrum Scale (GPFS): RDMA-enabled network adapter failure on the NSD server may result in file IO error

    Abstract

    IBM has identified an issue with all IBM GPFS and IBM Spectrum Scale versions where the NSD server is enabled to use RDMA for file IO and the storage used in your GPFS cluster accessed via NSD servers (not fully SAN accessible) includes anything other than IBM Elastic Storage Server (ESS) or GPFS Storage Server (GSS); under these conditions, when the RDMA-enabled network adapter fails, the issue may result in undetected data corruption for file write or read operations.

    Problem Summary:

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-07-26T16:24:13Z  

    Flash (Alert): IBM Spectrum Scale and IBM Elastic Storage Server:  Performance monitoring component potentially running fileset quota sensor on more than one node causing additional load 

    Abstract

    IBM has identified a configuration issue with the performance monitoring component in IBM Spectrum Scale V4.2.2 and V4.2.3, and IBM Elastic Storage Server (ESS) 5.0 and 5.1.  The default configuration is monitoring the fileset quota usage hourly from all nodes in the cluster instead of just from one node.  This issue may cause more load on the system than needed and can contribute to an overload situation.

    See the complete Flash at: http://www.ibm.com/support/docview.wss?uid=ssg1S1010423

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-08-02T19:13:21Z  

    Flash (Alert):  IBM Spectrum Scale: AFM incorrectly replicates rename operations

    Abstract: 

    IBM has identified an issue with AFM in IBM Spectrum Scale V4.1.1.12 through V4.1.1.15 and V4.2.2.0 through V4.2.3.2 levels where AFM might incorrectly replicate the rename operations. This issue may cause undetected data loss due to some files missing at the target site.

    Problem Summary:

    If a file is renamed twice under the same directory, AFM might incorrectly rename the file at the target site. For example, if the rename sequence is file1 -> file2 and file3 -> file1, then file1 might get missed at the target site. This happens only if multiple threads are executing these rename operations in parallel and the second rename goes before the first one due to a missing dependency check.

    See the complete Flash at:  http://www.ibm.com/support/docview.wss?uid=ssg1S1010426

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-08-14T13:26:30Z  

    Security Bulletin: A vulnerability in Samba affects IBM Spectrum Scale SMB protocol access method (CVE-2017-9461)

    Summary

    A Samba vulnerability affects IBM Spectrum Scale SMB protocol access method which could allow denial of service, caused by
    improper handling of dangling symlinks in smbd. A remote attacker could exploit this vulnerability to cause a fd_open_atomic infinite
    loop with high CPU usage and memory consumption on the system.


    See the complete bulletin at http://www-01.ibm.com/support/docview.wss?uid=ssg1S1010376

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-09-14T14:27:05Z  

    Security Bulletin: IBM Spectrum Scale Object Protocols functionality is affected by a security vulnerability in Python (CVE-2017-2592)

    Summary
    IBM Spectrum Scale Object Protocols functionality is affected by a security vulnerability in Python that could allow a local authenticated attacker to obtain sensitive information, caused by including sensitive data in the CatchError class. A local attacker could exploit this vulnerability to obtain sensitive information. (CVE-2017-2592)

    See the complete bulletin at http://www-01.ibm.com/support/docview.wss?uid=ssg1S1010471

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-09-22T20:05:25Z  

    Flash (Alert):  IBM Spectrum Scale (GPFS) AFM incorrectly replicates data when write and truncate operations are interleaved

    Abstract:

    IBM has identified an issue with AFM in IBM GPFS (V3.5.0.0 through V3.5.0.34, or V4.1.0.0 through V4.1.0.8), or IBM Spectrum Scale (V4.1.1.0 through V4.1.1.16, or V4.2.0.0 through V4.2.3.4) levels where AFM might not transfer write operations completely when a file is truncated. This may cause a data mismatch between cache (or primary) and home (or secondary). This issue may result in undetected data corruption at home (or secondary).

     

    See the complete Flash at:  http://www.ibm.com/support/docview.wss?uid=ssg1S1010629

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-09-25T18:31:52Z  

    GPFS 4.2.2.2 is now available from IBM Fix Central:

    http://www-933.ibm.com/support/fixcentral

    Problems fixed in GPFS 4.2.2.2

    January 19, 2017

    * Fix a mmfsd daemon crash for assert rmsgP != __null.
    * Fix a problem in which mmcrrecoverygroup fails when the admin and daemon networks are different.
    This fix applies to GSS/ESS customers.
    * Fix a signal 11 that can occur with active AFM filesets and heavy IO.
    * This fix provides AIX encryption performance improvements.
    * Fix a problem where the system monitoring framework was not reacting to configuration changes.
    * Fix a problem in which the admin network is not listed in the output of "mmhealth node show network".
    * Fix a problem in which gpfs_getacl returns ENOSPC. This can occur when the acl length exceeds the
    size of the buffer provided.
    * Fix a problem in which gpfs.service gets disabled and ccrmonitor gets killed after upgraded.
    * Fix a problem in which RemoteCmd gets stuck waiting for the pcacheListMutex.
    * Fix a problem in which "mmhealth cluster show" shows the wrong information for the components
    which were unhealthy and then became HEALTHY, while the corresponding services were STOPPED, DISABLED or SUSPENDED.
    * Fix a multipath device failure that reads "blk_cloned_rq_check_limits: over max size limit" which can
    occur when kernel function bio_get_nr_vecs() returns a value which is larger than the value
    of max sectors of the block device.
    * Fix a problem with CES node fail-over when the failing CES node stays powered off.
    * Fix a problem where error messages regarding cesiplist were shown in
    /var/adm/ras/mmsysmonitor.log on non CES-enabled clusters.
    * Fix a problem in which mmbackup falsely claims skipped files if multiple tasks combine outputs.
    * Fix an issue in the AFM environment where reads and evictions of a file can cause deadlocks.
    * mmperfmon query option -N now supports the following inputs: node number, node short name, node full name, node ip address.
    * Fix a 'isValidSocket(sock)' assertion that can occur when the incoming CCR request
    rate is much higher than the CCR server can handle.
    * This update addresses the following APARs: IV92103 IV92104 IV92105 IV92397 IV92398.

     

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-10-03T22:20:24Z  

    Technote (Troubleshooting):  IBM Spectrum Scale: SMB cluster export services (CES) must not be upgraded concurrently

    Problem (Abstract):
    SMB cluster export services (CES) within IBM Spectrum Scale must not be upgraded concurrently nor have differing versions of the gpfs.smb rpm active across multiple CES nodes at once.

     

    See the complete Technote at:  http://www.ibm.com/support/docview.wss?uid=ssg1S1010619

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-10-03T22:21:25Z  

    Flash (Alert): IBM Spectrum Scale: Quick restart of ctdb under SMB load can lead to a race condition

    Abstract:
    IBM has identified an issue with IBM Spectrum Scale V4.2.0.x in which a quick restart of ctdb under SMB load can lead to a race condition that keeps ctdb stuck in an endless recovery. This can occur during upgrade or by rapidly bringing the SMB service online / offline.

     

    See the complete Flash at:  http://www.ibm.com/support/docview.wss?uid=ssg1S1010618

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-10-09T19:17:16Z  

    Flash (Alert):  IBM Spectrum Scale (GPFS) V4.1 and 4.2 levels: network reconnect function may result in file system corruption or undetected file data corruption

    Abstract
    IBM has identified a problem with IBM Spectrum Scale (GPFS) V4.1 and V4.2 levels, in which resending an NSD RPC after a network reconnect function may result in file system corruption or undetected file data corruption.


    See the complete Flash at:  http://www.ibm.com/support/docview.wss?uid=ssg1S1010668

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-10-09T19:17:54Z  

    Technote (Troubleshooting):  IBM Spectrum Scale support:  mmchfs -V full command will fail on upgrade from file system 2.2

    Problem (Abstract):
    If your file system version is still at the 2.2 level, then running mmchfs -V full on certain levels of IBM Spectrum Scale will cause the mmchfs command to fail.  The file system will be unusable until the fix is applied.

     

    See the complete Technote at:  http://www.ibm.com/support/docview.wss?uid=ssg1S1010654

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-11-28T13:29:42Z  

    Security Bulletin: Vulnerabilities in Samba affect IBM Spectrum Scale SMB protocol access method (CVE-2017-12163, CVE-2017-12151, CVE-2017-12150)

    Summary

    Vulnerabilities in Samba affect IBM Spectrum Scale SMB protocol access method that:
    - could allow a remote authenticated attacker to obtain sensitive information, caused by a memory leak over SMB1 (CVE-2017-12163)
    - could provide weaker than expected security, caused by the failure to properly sign and encrypt DFS redirects when the max protocol for the original connection is set as ''SMB3'' (CVE-2017-12151)
    - could allow a remote attacker to obtain sensitive information, caused by the failure to require SMB signing in SMB1/2/3 connections (CVE-2017-12150)

     

    See the complete bulletin at http://www-01.ibm.com/support/docview.wss?uid=ssg1S1010703

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-11-30T22:25:58Z  

    Technote (troubleshooting): IBM Spectrum Scale v4.2.x may experience cluster hangs, unacceptably high CPU load spikes, or high Command Line Interface command execution time on IBM System z14

    Problem (Abstract)

    Core components of Spectrum Scale initialize and use encrypted communication. This communication is happening whenever certain Spectrum Scale commands are performed, even when the system appears to be idle. Depending on the IBM System z14 configuration, cluster hangs may occur. In addition, encryption initialization may temporarily spike CPU usage to 100% and response times will slow down to unreasonable speeds.

    IBM has corrected the issues in IBM Spectrum Scale v4.2.3.6 and later releases for zLinux only.

     

    See the complete Technote at:  http://www.ibm.com/support/docview.wss?uid=ssg1S1010859

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2017-12-12T14:42:14Z  

    Technote (troubleshooting): IBM Spectrum Scale: Using O_DIRECT and fork(2) in the same process in Linux

    Problem(Abstract):
    IBM Spectrum Scale: Using O_DIRECT and fork(2) in the same process in Linux

    Symptom:
    System call read() may fail to record data into the user buffer when direct I/O is used, that is, when specifying the O_DIRECT flag when opening the file.

     

    See the complete Technote at:  http://www.ibm.com/support/docview.wss?uid=ssg1S1010878

     

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2018-02-02T18:01:29Z  

    Flash (Alert):  IBM Spectrum Scale (GPFS):  Undetected corruption of archived sparse files (Linux)

    Abstract

    IBM has identified an issue with IBM GPFS and IBM Spectrum Scale for Linux environments, in which a sparse file may be silently corrupted during archival, resulting in the file being restored incorrectly.

     

    See the complete Flash at:  http://www.ibm.com/support/docview.wss?uid=ssg1S1012054

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2018-02-26T15:29:53Z  

    Security Bulletin: A vulnerability has been identified in IBM Spectrum Scale that could allow a local unprivileged user access to information located in dump files. User data could be sent to IBM during service engagements (CVE-2017-1654).

    Summary
    A vulnerability has been identified in IBM Spectrum Scale that could allow a local unprivileged user access to information located in dump files. User data could be sent to IBM during service engagements (CVE-2017-1654).

    See the complete bulletin at http://www-01.ibm.com/support/docview.wss?uid=ssg1S1010869

  • gpfs@us.ibm.com
    gpfs@us.ibm.com
    662 Posts

    Re: IBM Spectrum Scale V4.2.2 announcements

    ‏2018-03-02T17:09:32Z  

    Security Bulletin:  Vulnerabilities in Samba affect IBM Spectrum Scale SMB protocol access method (CVE-2017-14746, CVE-2017-15275)

    Summary

    Vulnerabilities in Samba affect IBM Spectrum Scale SMB protocol access method that:
    - could allow a remote attacker to execute arbitrary code on the system, caused by a use-after-free memory error (CVE-2017-14746)
    - could allow a remote attacker to obtain sensitive information, caused by a heap memory information leak (CVE-2017-15275)

    See complete bulletin at:  http://www.ibm.com/support/docview.wss?uid=ssg1S1012067