How to determine which device cannot be accessed by vxconfigd from the contents of the error message: dmp_tur_temp_pgr: open failed: error = 6 dev=0x110/0x42

Article:TECH69044  |  Created: 2009-01-24  |  Updated: 2010-01-07  |  Article URL http://www.symantec.com/docs/TECH69044
Article Type
Technical Solution

Product(s)

Environment

Issue



How to determine which device cannot be accessed by vxconfigd from the contents of the error message: dmp_tur_temp_pgr: open failed: error = 6 dev=0x110/0x42

Error



VxVM vxdmp 0 dmp_tur_temp_pgr: open failed: error = 6 dev=0x110/0x42

Solution




What does the message "dmp_tur_temp_pgr: open failed: error = 6 dev=0x110/0x42" mean

The function dmp_tur_temp_pgr is used by vxconfigd to place temporary reservation keys on a device to enable the system in question to access the device.
You will see this type of messages when the device is not accessible or the environment does not support SCSI3 Persistent Group Reservations (PGR).
dmp = dynamic multipathing
tur = test unit ready
temp = temporary
pgr = persistent group reservations


How to determine which device cannot be accessed by vxconfigd

Example:
---------------------------
Mar 10 07:06:46 iedadu002 vxdmp: [ID 238993 kern.notice] NOTICE: VxVM vxdmp 0 dmp_tur_temp_pgr: open failed: error = 6 dev=0x110/0x42
Mar 10 07:06:46 iedadu002 vxdmp: [ID 238993 kern.notice] NOTICE: VxVM vxdmp 0 dmp_tur_temp_pgr: open failed: error = 6 dev=0x110/0x42
Mar 10 07:06:46 iedadu002 vxdmp: [ID 238993 kern.notice] NOTICE: VxVM vxdmp 0 dmp_tur_temp_pgr: open failed: error = 6 dev=0x110/0x42
---------------------------

The device information consists of two hexadecimal values: dev=0x110/0x42, the first is the major number and the second is the minor number.
convert to decimal:
0x110 = 272 (major number)
0x42 = 66 (minor number)

Let us have a look at the /dev/vx/dmp folder which device owns these major and minor numbers:

root@iedadu002 -> ls -la /dev/vx/dmp
brw------- 1 root other 272, 66 Jan 29 19:55 c3t0d57

This shows the major and minor numbers belong to device c3t0d57.

The vxdisk list output shows the device is in error status, meaning Volume Manager cannot access the device.

root@iedadu002 -> vxdisk -o alldgs list
c3t0d57s2 auto - - error

This confirms that Volume Manager was not able to access the device, which is the cause of the error message.


Possible causes of device in error status

- Hardware device defect
- The device is not yet labeled or there is no partition table.
- Partition 2 does not represent the entire device (prtvtoc /dev/dsk/c3t0d57s2)
- There is no read/write permission on the device (check the permission on the storage)
- SCSI3 PGR is not supported on the device.




Legacy ID



321457


Article URL http://www.symantec.com/docs/TECH69044


Terms of use for this information are found in Legal Notices