A newer release of this product is available.
lmgr.mismatch events
Contributors
Suggest changes
PDFs
lmgr.mismatch.file.objects
- Severity
-
NOTICE
- Description
-
This message occurs when the current file object of a lock does not match the file object found through the file handle. This might be caused by a SnapMirror® promote operation where the Master Data Set ID (MSID) is remapped.
- Corrective Action
-
None.
- Syslog Message
-
(None).
- Parameters
-
volume (STRING): Name of the volume, based on the file handle.
lockid (STRING): Lock Universal Unique Identifier (UUID) of the sharelock.
caller (STRING): WAFL® spinnp operation that encountered this event.