Readme and Release notes for release 5.0.0.1 IBM Spectrum Scale 5.0.0.1 Spectrum_Scale_Protocols_Standard-5.0.0.1-ppc64-Linux Readme

Unless specifically noted otherwise, this history of problems fixed for IBM Spectrum Scale 5.0.x applies for all supported platforms.

Problems fixed in GPFS 5.0.0.1 [February 7, 2018]

• Fix offline fsck deadlocks that can occur when there is orphaning inodes IJ02867.
• Fix the pending log file migration assert that can occur when doing file system restripe operations or adding/deleting/changing the file system disks IJ02867.
• Fix a problem in which if inode expansion is interrupted, it may leave nAllocatedInodes inconsistent between sg descriptor and the fileset metadata file IJ03146.
• Change code to recover corrupted files in CCRs committed directory during GPFS startup to prevent these corrupted files causing other components to fail IJ03144.
• Address a problem where a user cannot make changes to the afmTarget once he has created the fileset with a wrong mapping name (or) host name in the afmTarget field IJ02867.
• Fix node hangs due to consumption of DMAPI event mailboxes IJ03141.
• Fix a log assert which may happen during mmdelsnapshot if a file in the snapshot has a DITTO xattr overflow block address IJ02867.
• If HAWC is enabled for a file system for which log recovery has failed, the recovery log is no longer dumped, because the recovery log may contain user data. Also, dump files are now created with more restricted permissions IJ02867.
• Fix a gpfsReserveDelegation exception which can occur if a kworker returns a nfs4 lease IJ02867.
• Address the issue to find latest common RPO snapshot between acting and old primary to trigger a restore in failbacktoprimary IJ02867.
• Fix a rare case long waiters 'waiting for new SG mgr' which may happen if a file system has no external mounts and 'tsstatus -m ' command is run on the fs manager node in a specific time window IJ02867.
• Fix a sample script filehist that may fail with divide by zero error IJ03142.
• Fix the orphan inode issue found after a deletion of the dependent fileset. This only refers to encrypted clone files while doing fileset deletion and only if the key management server is unavailable IJ02867.
• Address the issue of a valid return code being returned even if the failback command failed to execute. This does not occur with IW filesets IJ02867.
• Fix a mmfsd assert at: Assert exp(mdiBlockP != __null) ts/vdisk/mdIndex.C 2299. This can happen during a vdisk creation and the repair thread trying to harden the metadata onto the disk IJ02867.
• Fix erratic inode expansion behavior and spurious 'Expanded inode space' log messages under multi-node create workload IJ02867.
• Address a problem where a deadlock can happen if there is application IO occurring to the AFM fileset when the home/secondary site fileset has gone stale IJ02867.
• Fix Assert exp(inodeFlushFlag) openinst-vfs.C 1560 that can occur while updating extended attributes IJ02867.
• Fix assert exp(!"oldDiskAddrFound.compAddr(*oldDiskAddrP)") which may happen when you preallocate data in an inode file. Note, fallocate() on GPFS file system or write()/fallocate() on a FPO file system can trigger preallocations IJ03163.
• Fix an issue in the AFM environment where inband trucking tries to copy the data back to secondary even though the data already exists IJ02867.
• Fix a problem in which incorrect node address managed in RGCM keeps causing RG to be resigned and recovery failure when primary node is down IJ03247.
• Fix an issue in the AFM environment where some files are moved to .ptrash directory intermittently over GPFS backend IJ03148.
• Fix a problem where the Receive Worker threads go CPU bound after a kernel crash IJ03147.
• Fix a ganesha kernel crash IJ02867.
• Fix a hang during unmount which can occur if QOS has been enabled on any file system IJ02867.
• Fix a deadlock that can occur during file system repair IJ02867.
• Fix a problem in which mmfileid fails to list small files IJ03156.
• Fix a deadlock involving a failed "mmfsctl resume" command, a SG panic and while having disk issues IJ02867.
• Fix a rare race during DA integrity manager service state transition, which may cause assert like "Assert exp(nIMTasks == 0" IJ02867.
• Fix a rare case that truncate() does not set file size correctly. The file size is set to full block boundary incorrectly and the fragment is lost IJ03149.
• Fix a mmapplypolicy/tsapolicy core dump: ThreadThing::check mutexthings.C:170 and an improper recovery from helper failure during a directory scan IJ02867.
• Fix an issue in the AFM environment where already existing uncached files are not prefetched correctly IJ03150.
• Fix a log assert "Assert exp(totalSteps >= 0) in file workthread.C". It happens when running mmlsfileset -r or mmlsfileset -i command against a file system which has a huge inode number or lots of independent filesets IJ03233.
• Fix a problem where pmsensor service crashes because there are NULL entries returned from mmpmon for AFM filesets IJ03151.
• Fix a problem in which the fileset failed to run recovery during a failover IJ02867.
• Fix an issue in the AFM environment where daemon deadlocks during recovery with recursive dependent rename operations IJ02867.
• Fix a NUMA discovery problem for nodes with GPUs IJ03161.
• Fix a problem in which a directory inside an IW fileset cannot fetch new changes to the directory made at its home counterpart. This can happen following a recovery or failover that has been run on the IW fileset at the cache site IJ02867.
• Fix a problem in which mmfsck will fail with "There is not enough free memory available for use by mmfsck in ..." due to a memory leak IJ02867.
• Fix problem that could cause count of read() or write() calls to be under-counted in application I/O mmpmon and performance monitor metrics IJ02867.
• Fix an issue in the AFM environment where files are moved to .ptrash during the rename on independent-writer mode filesets IJ02867.
• Fix a mount failure by allowing getEFOptions to work even if it can't get a local environment lock as long as it can access the latest mmsdrfs file IJ03236.
• Fix fcntl performance issue IJ03152.
• Fix a locking issue during prefetching of a directory block that can lead to a FSSTRUCT error being incorrectly issued. This could happen when there is a race between expanding the first directory block on one node and prefetching of the same block on another node IJ02867.
• Fix a recall problem on AIX that can occur during reads and writes of a non-resident file IJ02867.
• Fix a problem that could cause mmpmon histograms not to be updated while doing sequential I/O of less than the file system block size IJ02867.
• Fix an issue in the AFM environment where gateway nodes crashes intermittently. Also fix an issue where lookup returns incorrect results IJ02867.
• Fix a rare timing assertion when the file system is forced to unmounted at the same time that quota files are being flushed to disk IJ02867.
• Fix problems with network monitoring caused by names like loop@loop IJ02867.
• This fix will ensured that server reachability is accurately reported for multiple servers with CES stack configured for LDAP authentication IJ03796.
• Fix a problem where on AIX mmcrnsd call clears out the PVID that was assigned by the OS IJ03159.
• Fix an unnecessary file system panic and unmount on client nodes during mmchdisk start command. The file system panic/unmount could occur when a disk which has been started becomes unavailable again in the middle of mmchdisk start command IJ03238.
• Fix a problem where, when a recovery policy fails with an error 2, we need to rerun the policy with higher debug level for policy IJ02867.
• Fix an issue where recovery was stuck in the local cluster due to GW node changes in a remotecluster environment IJ02867.
• This fix adds a protection to prevent a compressed fragment from being expanded without being uncompressed first in some unexpected conditions of having inconsistent compression flags. This fix also replaces an assert with an IO error to minimize the user impact IJ03153.
• Fix an issue that remote NSD clients drop into a long time retry loop during an ESS outage. This can occur when there are multiple ESS building blocks and GPFS replication is enabled in the cluster. When shutting down both servers of a ESS building block simultaneously, remote NSD clients can experience a long retry loop like 'waiting for stateful NSD server error takeover (1)' IJ03154.
• Fix the code to call the tiebreakerCheck user exit script in case the CCR is enabled IJ02867.
• Fix a problem where recovery keeps failing with an error 2 because the AFM recovery script wasn't able to handle directory names in the fileset that had trailing spaces in them IJ03157.
• This fix Adds a new config option numactlOptioni for setting NUMA nodes the GPFS daemon can allocate from IJ03158.
• This fix Adds a hidden option to set a file/dir as local using the mmafmctl script so that it doesn't replicate the changes on the file/dir to the secondary/home site IJ02867.
• This fix synchronizes write failures and read operations to avoid reading stale data from disk IJ02867.
• RGCK might be used very rarely in the case of RG recovery failure. Fix an assert like "logAssertFailed: OWNED_BY_CALLER(lockWordCopy, lockWordCopy)" when trying to revive a defective pdisk in RGCK IJ02867.
• This fix Addresses a problem where reading a symbolic links pointing to nothing at home can cause an Assert at the cache site IJ03239.
• Fix a Object Authentication(Keystone) configuration failure that occurs on External Keystone with the v3 api IJ02867.
• Fix a problem where AFM/DR recovery can cause buffer overflows for path names that are really long (beyond 1024 characters) IJ02867.
• Fix an issue in the AFM environment where a file listing during readdir fails for dirty files in local-updates mode. This problem happens with a ganesha NFS server having AFM local-updates mode fileset exports IJ03425.
• Fix a problem in which gpfs.snap stops with an error message when it stores (TARs) log files IJ03847.
• Fix a problem in which open(O_TRUNC) returns with an error but still truncates the file IJ03850.
• This update addresses the following APARs: IJ02867 IJ03141 IJ03142 IJ03144 IJ03146 IJ03147 IJ03148 IJ03149 IJ03150 IJ03151 IJ03152 IJ03153 IJ03154 IJ03156 IJ03157 IJ03158 IJ03159 IJ03161 IJ03163 IJ03233 IJ03236 IJ03238 IJ03239 IJ03247 IJ03368 IJ03425 IJ03688 IJ03796 IJ03847 IJ03850

Unless specifically noted otherwise, this history of problems fixed for IBM Spectrum Scale 5.0.0 applies for all supported platforms.

Problems fixed in Spectrum Scale Protocols Packages 5.0.0-1 [Feb 7, 2018]

• callhome: callhome misses net/dev details and cluster details
• ces: Protocol nodes doesn't display CES IP appropriately
• ces: mmces address prints twice when the wrong command line option is passed
• ces: mmhealth node show THRESHOLD stuck in CHECKING
• ces: mmces service 'start' 'OBJ' -N CESNODES is not successfully executed, the exit code 0
• ces: mmhealth reports ib_rdma_ports_wrong
• ganesha: Kernel crashes in ganesha.nfsd
• ganesha: build Tag: V2.5.3-ibm012.00
• obj: Updated spectrum-scale-object rpm and deb to 5.0.0-1 release
• obj: Updates spectrum-scale-object-selinux rpm to 5.0.0-1 release
• obj: Updated pmswift rpm and deb to 5.0.0-1 release
• obj: Added suport for disabling container updates for object operations on swift
• obj: Objectizer performance enhancements on swiftonfile to ask gpfs policy engine to define split points at every container and to identify containers with no files in it.
• obj: Make URL markers safe for objectizer on swiftonfile
• smb: getgrgid call does not return information for well-known SID
• smb: "mmsmb config list --supported", doesn't work expected
• smb: mmsmb exportacl list creates wrong output as some conditions
• smb: add gpfs.smb 4.6.11_gpfs_29-1

Problems fixed in Spectrum Scale Protocols Packages 5.0.0-0 [Dec 15, 2017]

• Please see the "What's New" page in the IBM Knowledge Center