Re: SCSI reservation conflicts after update

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





christopher barry wrote:
On Fri, 2008-03-28 at 21:03 -0400, Sajesh Singh wrote:
  
After updating my GFS cluster to the latest packages (as of 3/28/08) on 
an Enterprise Linux 4.6 cluster (kernel version 2.6.9-67.0.7.ELsmp)  I 
am receiving scsi reservation errors whenever the nodes are rebooted. 
The node is then subsequently rebooted at varying intervals without any 
intervention. I have tried to disable the scsi_reserve script from 
startup, but it does not seem to have any effect. I have also tried to 
use the sg_persist command to clear all reservations with the -C option 
to no avail. I first noticed something was wrong when the 2nd node of 
the 2 node cluster was being updated. That was the first sign of the 
scsi reservation errors on the console.

 From my understanding persistent SCSI reservations are only needed if I 
am using the fence_scsi module.

I would appreciate any guidance.

Regards,

Sajesh Singh

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
    


Sajesh, start here:
http://www.mail-archive.com/linux-cluster@xxxxxxxxxx/msg01029.html

I went through this too, and Ryan helped me out a lot!

Good Luck!
-C
  
Christopher,
               I have read through the entire posting and a bit of information seems to be missing. Did you fix it by simply disabling the scsi_reserve script and clearing the stale reservations ?

Thanks,

Sajesh
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux