Atomic Test And Set Of Disk Block Returned False For Equality [ 2024-2026 ]

The host sent a command saying: "I want to lock this block. I expect the current owner ID to be 'X'." The storage array looked at the block, saw that the ID was actually 'Y', and replied: "False. The data is not what you expected." Common Causes

Let’s parse the error into its core components: The host sent a command saying: "I want to lock this block

dlm: atomic test and set of disk block 1048576 returned false for equality (expected=0, got=1002) dlm: lock acquisition failed. Node 1002 already owns the lock. Node 1002 already owns the lock

“The atomic test-and-set operation on the disk block returned false when checking for equality, indicating that the current value in the block did match the expected value. This suggests a concurrent modification or a stale expected value — the operation failed as designed, preventing a potential race condition or lost update.” Further investigation and debugging are necessary to resolve

The observation that an atomic test and set operation on a disk block returned false for equality highlights a potential issue with data consistency or concurrent access. Further investigation and debugging are necessary to resolve the root cause and ensure the reliability of disk operations.