General
1837047 Members
2984 Online
110111 Solutions
New Discussion

Invalid reservation type

 
Jian-ping Hui
Occasional Contributor

Invalid reservation type

Hi,

We have two machines sharing a lun /dev/rdisk/disk77.
disk 77 64000/0xfa00/0xb7 esdisk CLAIMED DEVICE online HP A6218A
0/3/1/0.0x50060b000019c87b.0x4005000000000000
0/3/1/1.0x50060b000019c883.0x4005000000000000
/dev/disk/disk77 /dev/rdisk/disk77


By issuing "PERSISTENT RESERVE IN" command with the action "READ KEYS", we can see there is no registration on the lun. Below is the output of "PERSISTENT RESERVE IN" with "READ KEYS":
00 00 00 00
00 00 00 00

According to the SPC-3 standard, the format of the output buffer should be:
[PRGENERATION][][][]
[ADDITIONAL LENGTH (n-7)][][][]
Based on the above format, we can see the additional length for the output is 0. This means there is no registrations on the lun.


But if we issue "PERSISTENT RESERVE IN" command with the action "READ RESERVATIONS", we will get the buffer like below:
00 00 00 00 00 00 00 10 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00

According to the SPC-3 standard, the format of the output buffer should be:
(1) If there is no reservations:
[PRGENERATION][][][]
[0][0][0][0]
(2) If there are reservations existing:
[PRGENERATION][][][]
[0][0][0][10]
[RESERVATION KEY][][][][][][][]
[Obsolete]
[Reserved]
[Scope|-|-|-|Type|-|-|-]
[Obsolete][]

In our actual output data, the additional length is 0x10. It means there are reservations. Also, reservation keys and type are 0.

According to the SPC document, this case is invalid. I have no idea what's wrong in the lun. Could anybody give some helps? Appreciate for your any helps in advance.

Thanks again.