Red Hat Bugzilla – Bug 409381
fence_scsi: service scsi_reserve restart not present.
Last modified: 2009-05-18 17:16:22 EDT
Description of problem: I attempted to "unfence" a node by restarting the scsi_reserve service, however running 'service scsi_reserve restart' did nothing. I had to run 'service scsi_reserve stop && service scsi_reserve start' Should restart be implemented in the init script? If we don't support restart there should be some output saying as much when a user attpemts a restart. Version-Release number of selected component (if applicable): fence-1.32.50-2.fencescsi.test.patch
You can simply run 'scsi_reserve start', which will register the node with all relevant devices. If the reservation already exists, it does nothing. I could implement a 'restart' command if it seems like the right thing to do. Keep in mind that unlike other services, scsi_reserve is not a long-running process (daemon). So would restart actually unregister and re-register the node with all the devices? Or simply re-run the registration (start)?
Fixed in RHEL4. The fix for this is not truly a restart, but I don't think that is what we want for this particular script. In my opinion, a *true* restart would be to remove (unregister) our key from all devices and the re-register our key with all devices. We want to avoid removing the key. As soon as the key is remove, the node has no write access to the disk(s). For fencing via SCSI-3 reservations, this is as good as being fenced. Its best that we avoid removing keys from the devices. The way I have "restart" implemented now is to do almost exactly what "start" does. If the script is called with the "restart" option, we simply get a list of all devices within cluster volumes and register our key with those devices. It does not matter if our node/key is already registered because of the way we create the registration. Then we check to see if a reservation exist for the device, and if not, we create the reservation.
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 therefore 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-2009-1050.html