Sun Cluster 3.2 & SCSI Reservation Issues

Sun Cluster 3.2 & SCSI Reservation Issues

If you have worked with luns and Sun Cluster 3.2, you may have discovered that if you ever want to remove a lun from a system, it may not be possible because of the scsi3 reservation that Sun Cluster places on the disks.  The example scenario below walks you through how to overcome this issue and proceed as though Sun Cluster is not even installed.

Example:  We had a 100GB lun off of a Hitachi disk array that we were using in a metaset that was  controlled by Sun Cluster. We had removed the resource from the  Sun Cluster configuration and removed  the device with configadm/devfsadm,  however when the storage admin attempted to remove the lun id from the Hitachi array zone,  the Hitach array indicated the lun was still in use.   From the Solaris server side, it did not appear to be in use,  however Sun Cluster has set the scsi3 reservations on the disk.

Clearing the Sun Cluster scsi reservation steps

Determine what DID device the lun is mapped to using /usr/cluster/bin/scdidadm -L

Disable failfast on the DID device using /usr/cluster/lib/sc/scsi -c disfailfast -d /dev/did/rdsk/DID

Release the DID device using  /usr/cluster/lib/sc/scsi -c release -d /dev/did/rdsk/DID

Scrub the reserve keys from the DID device using  /usr/cluster/lib/sc/scsi -c scrub -d /dev/did/rdsk/DID

Confirm reserve keys are removed using /usr/cluster/lib/sc/scsi -c inkeys -d /dev/did/rdsk/DID

Remove lun from zone on machine or whatever procedure you were trying to complete.