The scsi_reserve init script produces "reservation conflict" messages in /var/log/messages. Appears this is due to calling sg_persist to create registration without checking to see if key is already registered. Possible solutions include checking for existing registration or us the "register and ignore" option for sg_persist.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Fixed. The scsi_reserve script now calls sg_persist with -I option, which registers a key with a device and ignores any previous keys registered for the I_T nexus. The cause of the "reservation conflict" messages at startup were due to the fact that the node (I_T nexus, really) already had a key registered on that device. We would see a "reservation conflict" message for each device. This fix will ignore any existing registrations for the I_T nexus. Thus, each time we run 'scsi_reserve start' it will overwrite any existing registrations for that I_T nexus.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0347.html