Warning and Info Messages
This section describes runtime error messages. For information about other types of runtime messages, see Alerts Playbook and Error Messages.
The alerts are grouped into the following categories:
Stopping Transformation of a File on Volume Dismount (Windows only)
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]
Issues with Policy or System Configuration
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
Failure to Enable GuardPoint During Cleanup
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.
General LDT Operations
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]
Missing LDT extended attribute
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.
Locking Contention
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]
Initiation and completion of LDT metadata cleanup
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]
