Anyone seen this before? I've seen some posts regarding RESERVATION_CONFLICT errors in general but nothing that matches exactly. In a 5 node cluster, I am seeing this on 2 of the nodes. I just happened upon it working on another issue. It's been happening for awhile and has not caused any noticeable problems.
Jun 7 12:11:57 host1 vmkernel: 45:14:24:01.230 cpu0:8423)SCSI: 4782: path vmhba1:1:3: Passing device status RESERVATION_CONFLICT (18) through
Jun 7 12:11:58 host1 vmkernel: 45:14:24:02.379 cpu0:1024)SCSI: 4782: path vmhba1:1:3: Passing device status RESERVATION_CONFLICT (18) through
Richard J Minick, VCP