Comment 1 for bug 1864419

Revision history for this message
Rafael David Tinoco (rafaeldtinoco) wrote :

Creating an easier reproducer:

Node 01:

rafaeldtinoco@clubionic01:~$ sudo sg_persist --out --register --param-sark=3abe0000 /dev/sdc
  Msft Virtual Disk 1.0
  Peripheral device type: disk

rafaeldtinoco@clubionic01:~$ sudo sg_persist --out --reserve --param-rk=3abe0000 --prout-type=5 /dev/sdc
  Msft Virtual Disk 1.0
  Peripheral device type: disk

rafaeldtinoco@clubionic01:~$ sudo sg_persist -r /dev/sdc
  Msft Virtual Disk 1.0
  Peripheral device type: disk
  PR generation=0xb, Reservation follows:
    Key=0x3abe0000
    scope: LU_SCOPE, type: Write Exclusive, registrants only

----

Node 02: (has to be able to remove node's 01 reservation):

rafaeldtinoco@clubionic02:~$ sudo sg_persist -v --out --release --param-rk=3abe0000 --prout-type=5 /dev/sdc
    inquiry cdb: 12 00 00 00 24 00
  Msft Virtual Disk 1.0
  Peripheral device type: disk
    Persistent Reservation Out cmd: 5f 02 05 00 00 00 00 00 18 00
persistent reserve out: transport: Host_status=0x07 [DID_ERROR]
Driver_status=0x00 [DRIVER_OK]

PR out (Release): Sense category: -1

We get a sense out of the storage server.

----

But if we try to remove the reservation from the same node it works:

rafaeldtinoco@clubionic01:~$ sudo sg_persist -v --out --release --param-rk=3abe0000 --prout-type=5 /dev/sdc
    inquiry cdb: 12 00 00 00 24 00
  Msft Virtual Disk 1.0
  Peripheral device type: disk
    Persistent Reservation Out cmd: 5f 02 05 00 00 00 00 00 18 00
PR out: command (Release) successful