Patch Note for v7.4.0.106

New Platform Support

The following kernel is supported starting with CTE 7.4.0.106:

SLES

• SLES 15 SP5 GA 5.14.21-150500.53-default

Resolved Issues

• AGT-45196: [CS1464844] Unable to reclaim the space with thin provisioning disks for ASMFD

  The issue was that SecVM support for discarding storage was not available for all devices which can support it. That has been fixed.

• AGT-45453: The voradmin ldt summary, and key report, should not include vorm_ldtprivspace for an LDT NFS GuardPoint

  Status reports produced by the voradmin command on LDT protected GuardPoints on NFS no longer include stats pertaining to LDT internal metadata files under the vorm_ldtprivspace subdirectory.

• AGT-45573: [CS1475593]: CTE breaks Samba on RHEL 8.5 and 9.2 - Unable to delete directories

  Error occurred due to the way a callback function handled metadata. This has been fixed.

• AGT-46369: On an LDT NFS GuardPoint, while single file rekey is running in a renamed directory, the secondary host receives sflock_iosize_key_off:2 when summing data files

  There was an inconsistency in caching/updating LDT rekey attributes, after rekey completion, between primary and secondary members of the LDT GuardPoint. This solution resolves possible data inconsistency across primary and secondary members after rekey completion.

• AGT-46510: Missing files caused GuardPoint to be stuck in "rekeying" state after demotion/promotion

  A deadlock after primary host self-demotion was caused by the loss of the NAS connection. This has been resolved.

• AGT-46558: GuardPoint stats mismatched after rekey

  LDT stats available for display through the voradmin command were not always properly updated from persistent stats when enabling the GuardPoint. This resulted in displaying stale LDT stats. The solution was to load the persistent LDT stats from the GuardPoint extended attributes during the guard operation, just before resuming rekey.

• AGT-46584: LDT went from status: busy unlink to rekeyed to releasing the file after unlock

  A crash occurred due to the cancellation of the LDT rekey operation on a file that had become unlinked. This has been resolved.

• AGT-46682: LDT status: resume during unguard: account for the filesystem no longer present

  Resolved a race between the process that disables the GuardPoint and enables the LDT resume operation. It attempted to resume LDT on the same GuardPoint after the GuardPoint was disabled.

• AGT-46855 [CS1484237]: Not able to guard a path with an LDT policy

  An interruption in launching LDT prior to the rekeying state would leave a GuardPoint in a state that would no longer guard due to the existence of an MDS file in a pre-launch state. The LDT recovery process was enhanced to detect and recover from early interruption in an LDT launch.