Warning and Info Messages

The following warning message is recorded when transformation of a file is stopped because the containing volume is dismounted.

• LDT: Volume dismounted. Aborting transformation at file [PathName]

The following warning messages are recorded when CTE cannot perform LDT on the GuardPoint, because there are errors in the policy associated with the GuardPoint, or the file system containing the GuardPoint is not supported by LDT. Files in the GuardPoint can still be accessed, but no LDT encryption occurs.

• LDT: The GuardPoint [GuardPoint] does not have a valid transformation policy, there is no new key rule

• LDT: The GuardPoint [GuardPoint] does not have a valid transformation policy, there is no key_op rule

• LDT: The GuardPoint [GuardPoint] does not support online rekey, only file operations from the offline data transform process will be allowed

LDT records the following informational message when a user attempts to enable a newly added GuardPoint. This message displays if the GuardPoint directory was previously guarded with an LDT policy and the LDT metadata cleanup is in progress when user is guarding under the new policy.

• LDT: Cannot enable GuardPoint [GuardPoint] during LDT clean-up process

Solution

Retry the operation once the cleanup completes.

The following informational messages are recorded during various LDT operations. No action is required.

• LDT: Successfully suspended rekey on GuardPoint [GuardPoint]

• LDT: Successfully suspended rekey on all GuardPoints

• LDT: Successfully resumed rekey on GuardPoint [GuardPoint]

• LDT: Successfully resumed rekey on all GuardPoints

• LDT: Rekey operation completed on GuardPoint [GuardPoint]

The following warning message reports that the file with the specified inode number in the specified GuardPoint directory does not have an LDT extended attribute, therefore, access to the file is denied.

• LDT: Extended attribute of inode [InodeNumber] is missing under GuardPoint [GuardPoint]

Solution

LDT cannot determine the encryption key associated with the data in the file, therefore, you can only remove the file.

The following messages are recorded during the rekey process on a file. When user access to the file is very high, it causes a high degree of locking contention between the rekey process and user access. The second message reports when the contention is no longer in effect and the rekey process has resumed accessing file to rekey.

• LDT: Exclusive access for rekey delayed on inode [InodeNumber]

• LDT: Exclusive access for rekey granted after delay on inode [InodeNumber]

The following messages are recorded at the beginning and completion of LDT metadata cleanup through voradmin command.

• LDT: Metadata will start getting removed from all files in GuardPoint [GuardPoint]

• LDT: Metadata has been removed from all files in GuardPoint [GuardPoint]

The following warning messages displays when offline dataxform command was accidentally executed on an active LDT GuardPoint.

Checking if <guardpoint> is a guard point with a rekey policy applied
The secfs component doesn't support data transform on <guardpoint>
Verify this is a guardpoint with valid data transformation policy, and check the system log files for any other problems. It may be
due to one or more of following reasons; 1.policy has no valid key rule(s), and/or 2. policy has no key_op rule, and/or 3. policy
has valid permit rule(s), and/or 4. policy rule that contains key_op in the action field also specifies other actions.

This action results in an input/output error when creating new files in the GuardPoint.

Solution

For auto GuardPoint:

1. Disable the GuardPoint on CipherTrust Manager.

2. Delete the dataxform_auto_lock file in the GuardPoint.

3. Enable the GuardPoint on CipherTrust Manager.

For a manual GuardPoint:

1. Unguard using secfsd -unguard <guardpoint>.

2. Delete the dataxform_auto_lock file in the GuardPoint.

3. Enable the GuardPoint using secfsd -guard <guardpoint>.

The following warning message displays when offline dataxform command was executed on an unguarded LDT GuardPoint.

dataxform command fails with file "<gp>" invalid xf mode

This action creates the dataxform_auto_lock file in the GuardPoint which causes the write error when creating new files in the GuardPoint, if the GuardPoint was enabled prior to deleting the file.

Solution

Before enabling the GuardPoint, delete the dataxform_auto_lock file in the GuardPoint.