Hi, On Tue, Feb 12, 2008 at 04:54:38PM +0100, Johan Hoeke wrote: > Dejan Muhamedagic wrote: > > > > Recently somebody also had difficulties with hbaping, but IIRC it > > was the other way around, i.e. the 64bit didn't work. How comes > > that you have hbaping at all? Do you use need that? > > > > Thanks, > > > > Dejan > > > Hi Dejan, > > Hmmm, didn't see that question coming. Doesn't everybody with a SAN and > heartbeat use hbaping? :)
Yes, most people do. :) > I use hbaping enable the cluster to failover if the SAN connection > breaks on one node. The individual nodes do not have redundant paths to > the SAN, so if a hba or a fibre cable on one node breaks, the resources > should migrate to the other node. > > Simply using the filesystem ocf monitor action isn't sufficient in our > case, the SAN mount is remounted empty and read only when the SAN switch > port is manually turned off to simulate problems. The filesystem monitor > action doesn't notice. > > Suggestions welcome, this recompiling thing is labor intensive. If I > don't need hbaping to make resources migrate in case of SAN problems, > that would be great. Sorry, somehow I must've missed that you were using a fibre channel attached storage. The hbaping should work. It apparently depends on a library (forgot the name), but looks like you're already past that. Hope that you're OK once those compile problems are resolved. There's no way around recompiling packages. Thanks, Dejan > > regards, > > Johan > > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
