[Pacemaker] Immediate fs errors on iscsi connection problem

ruslan usifov ruslan.usifov at gmail.com
Tue Apr 5 11:24:30 EDT 2011


GREAT THANKS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

It's work. But i have some little question, how can i got same effect on
windows? Windows ISCSI initiator (win 2008 server) breaks connections and
newer it restarts??

4 апреля 2011 г. 8:24 пользователь Vladislav Bogdanov
<bubble at hoster-ok.com>написал:

> Hi,
>
> 03.04.2011 22:42, ruslan usifov wrote:
> >     You need some tuning from both sides.
> >     First, (at least some versions of) ietd needs to be blocked (-j DROP)
> >     with iptables on restarts. That means, you should block all incoming
> and
> >     outgoing packets (later is more important) before ietd stop and
> unblock
> >     all after it starts. I use home-brew stateful RA for this, which
> blocks
> >     (DROP) all traffic to/from VIP in slave mode and passes it to a later
> >     decision (no -j) in master mode.
> >
> >
> >
> > Thanks for reply, But how to implemet this from pacemaker. Or i must to
> > modify inet.d scripts?
>
> You can try attached.
> This was a first trial to write RA... It may contain some wrong logic,
> especially with scores, but it works for me.
> It is intended to be colocated with IP-address resource:
> colocation col1 inf: FW:Master ip
> order ord1 inf: ip:start FW:promote
>
> Vladislav
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs:
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110405/72ec631a/attachment-0003.html>


More information about the Pacemaker mailing list