6027-3943 [W] Excessive timer drift with node now
number (number number)
lastLeaseReplyReceived number (number)
lastLeaseRequestSent number (number)
lastLeaseObtained number (number)
endOfLease number (number) leaseAge
number ticksPerSecond number.
Explanation
GPFS has detected an unusually large difference in the rate of
clock ticks (as returned by the times() system call) between the cluster node
and the cc-mgr node.
User response
Check error log for hardware or device driver problems that
might keep causing timer interrupts to be lost or the tick rate to change
dramatically.
