Fencing and Reservation Conflict
Hi to all
I have redhat linux 5.9 64bit with SFHA 5.1 SP1 RP4 with fencing enable ( our storage device is IBM .Storwize V3700 SFF scsi3 compliant
[root@mitoora1 ~]# vxfenadm -d
I/O Fencing Cluster Information:
================================
Fencing Protocol Version: 201
Fencing Mode: SCSI3
Fencing SCSI3 Disk Policy: dmp
Cluster Members:
* 0 (mitoora1)
1 (mitoora2)
RFSM State Information:
node 0 in state 8 (running)
node 1 in state 8 (running)
********************************************
in /etc/vxfenmode (scsi3_disk_policy=dmp and vxfen_mode=scsi3)
vxdctl scsi3pr
scsi3pr: on
[root@mitoora1 etc]# more /etc/vxfentab
#
# /etc/vxfentab:
# DO NOT MODIFY this file as it is generated by the
# VXFEN rc script from the file /etc/vxfendg.
#
/dev/vx/rdmp/storwizev70000_000007
/dev/vx/rdmp/storwizev70000_000008
/dev/vx/rdmp/storwizev70000_000009
******************************************
[root@mitoora1 etc]# vxdmpadm listctlr all
CTLR-NAME ENCLR-TYPE STATE ENCLR-NAME
=====================================================
c0 Disk ENABLED disk
c10 StorwizeV7000 ENABLED storwizev70000
c7 StorwizeV7000 ENABLED storwizev70000
c8 StorwizeV7000 ENABLED storwizev70000
c9 StorwizeV7000 ENABLED storwizev70000
main.cf
cluster drdbonesales (
UserNames = { admin = hlmElgLimHmmKumGlj }
ClusterAddress = "10.90.15.30"
Administrators = { admin }
UseFence = SCSI3
)
**********************************************
I configured the coordinator fencing so I have 3 lun in a veritas disk group ( dmp coordinator )
All seems works fine but I noticed a lot of reservation conflict in the messages
of both nodes
On the log of the server I am constantly these messages: /var/log/messages
Nov 26 15:14:09 mitoora2 kernel: sd 7:0:1:1: reservation conflict
Nov 26 15:14:09 mitoora2 kernel: sd 8:0:0:1: reservation conflict
Nov 26 15:14:09 mitoora2 kernel: sd 8:0:1:1: reservation conflict
Nov 26 15:14:09 mitoora2 kernel: sd 10:0:0:1: reservation conflict
Nov 26 15:14:09 mitoora2 kernel: sd 10:0:1:1: reservation conflict
Nov 26 15:14:09 mitoora2 kernel: sd 9:0:1:1: reservation conflict
Nov 26 15:14:09 mitoora2 kernel: sd 9:0:0:1: reservation conflict
Nov 26 15:14:09 mitoora2 kernel: sd 7:0:1:3: reservation conflict
Nov 26 15:14:09 mitoora2 kernel: sd 8:0:0:3: reservation conflict
Nov 26 15:14:09 mitoora2 kernel: sd 8:0:1:3: reservation conflict
Nov 26 15:14:09 mitoora2 kernel: sd 10:0:1:3: reservation conflict
You have any idea?
Best Regards
Vincenzo
Hi
As I mentioned in first post on this thread ,I was in the same opinion that these messages are ignorable (if there are no operational issues) .. was expecting that support would say the same .. however good to have confirmation that its identified bug & would be fixed...
thx for the update ..
G
