- dmp_fast_recovery is set to off
# vxdmpadm gettune dmp_fast_recovery
Tunable Current Value Default Value
------------------------------ ------------- -------------
dmp_fast_recovery off on
- System messages shows reservation conflict messages
kernel: VxVM vxdmp V-5-0-0 SCSI error opcode=0x5f returned rq_status=0x12 cdb_status=0x1 key=0x6 asc=0x2a ascq=0x3 on path 8/0x90
kernel: sd 2:0:0:1: reservation conflict
kernel: sd 2:0:0:1: Unhandled error code
kernel: sd 2:0:0:1: SCSI error: return code = 0x00110018
kernel: Result: hostbyte=invalid driverbyte=DRIVER_OK,SUGGEST_OK
- dmpevents.log shows I/O error for other paths
I/O error occurred on Path sdg belonging to Dmpnode emc0_03f8
I/O analysis done as DMP_PATH_OKAY on Path sdg belonging to Dmpnode emc0_03f8
Marked as ioerr Path sdg belonging to Dmpnode emc0_03f8
I/O error occurred on Path sdg belonging to Dmpnode emc0_03f8
Unmarked as ioerr Path sdg belonging to Dmpnode emc0_03f8
- vxfenadm shows only 1 key is registered confirming missing keys for remaining paths.
# vxfenadm -s /dev/vx/dmp/emc0_03f8
Reading SCSI Registration Keys...
Device Name: /dev/vx/dmp/emc0_03f8
Total Number Of Keys: 1
key[0]:
[Numeric Format]: 66,86,67,83,0,0,0,0
[Character Format]: BVCS
[Node Format]: Cluster ID: unknown Node ID: 1 Node Name: testsys1
This is a known incident 2928764
When dmp_fast_recovery is off, the reservation flag is not set properly, due to which for the remaining paths the registration command fails with the transport error and PGR keys doesn't get registered. This results in subsequent reservation conflict messages.
But when dmp_fast_recovery is on the reservation flag is set correctly and hence this issue is not seen.
This issue has been fixed for
5.1SP1 : From 5.1SP1RP3P1 onwards
6.0.1: From 6.0.3 onwards
These patches can be obtained from SORT https://sort.Veritas.com/patch/finder
Applies To
SFHA 5.1SP1 and 6.0.1 on RHEL 5/6 or SLES 10/11