Veritas Volume Manager 5.1 Diskgroup imports fails with vxdmp V-5-0-0 due to registered fencing keys

book

Article ID: 100004232

calendar_today

Updated On:

Description

Error Message

# vxdg import datadg
Dec 18 09:32:37 BARNEY vxdmp: NOTICE: VxVM vxdmp V-5-0-0 i/o error occured (errno=0x5) on dmpnode 316/0x19b
Dec 18 09:32:37 BARNEY vxdmp: [ID 443116 kern.notice] NOTICE: VxVM vxdmp V-5-0-0 i/o error occured (errno=0x5) on dmpnode 316/0x19b

 

For new VxVM versions, you may also see

# vxdg import datadg
VxVM vxdg ERROR V-5-1-19179 Disk group datadg: import failed:
SCSI-3 PR Reservation Conflict error

Cause

The vxprivutil is capable of capturing the diskgroup configuration details.


# /etc/vx/diag.d/vxprivutil dumpconfig /dev/rdsk/c#t#d#s3 > /dg.dump


The dumpconfig details can be validated.


# cat dg.dump | vxprint -D - -qht


On closer inspection, keys are registered against the disk in question.


# vi /tmp/disks
/dev/rdsk/c3t5006048C53697980d55s2


To validate if keys are registered, in this instance they are.


# vxfenadm -g all -f /tmp/disks

 

For later versions, use

 

# vxfenadm -s all -f /tmp/disks
 

Resolution

Remove the keys registered against the disk in question for the "datadg" diskgroup.



# vxfenadm -a -k TMP -f /tmp/disks

# vxfenadm -c -k TMP -f /tmp/disks

 

Now try and import the impacted diskgroup

# vxdg import datadg


The diskgroup now imports fine.

 

Applies To

Solaris Volume Manager 5.1 onwards

Issue/Introduction

Veritas controlled diskgroup "datadg" can be imported on host "A" running Volume Manager 4.1, however, fails to import on host "B" running Volume Manager 5.1.