<div class="gmail_quote">On Fri, Mar 12, 2010 at 10:06 AM, Lars Ellenberg <span dir="ltr"><<a href="mailto:lars.ellenberg@linbit.com">lars.ellenberg@linbit.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, Mar 11, 2010 at 08:00:35PM +0000, Joseph L. Casale wrote:<br>
> When using drbd with cman under Redhat Cluster Suite, I need drbd to start<br>
> before cman so I edit the init scripts as follows:<br>
><br>
> sed -i "s/^# chkconfig: 345 70 08/# chkconfig: 345 20 80/g" /etc/rc.d/init.d/drbd<br>
> sed -i "s/^# Required-Start: \$local_fs \$network \$syslog/# Required-Start: \$network \$syslog/g" /etc/rc.d/init.d/drbd<br>
> sed -i "s/^# Required-Stop: \$local_fs \$network \$syslog/# Required-Stop: \$network \$syslog/g" /etc/rc.d/init.d/drbd<br>
><br>
> Are there any caveats to this I overlook? The $local_fs requirement causes it<br>
> to start after cman.<br>
<br>
</div>Why would cman provide "local" fs?<br>
<br>
Anyways, all that matters is that<br>
both the start order,<br>
and the stop order,<br>
are correct.<br>
So if the result of that modification works for you, go for it.<br>
<font color="#888888"><br></font><div><div class="h5"><br>
</div></div></blockquote></div><br><div>under which version of OS?</div><div>In RH EL 5.4 you have 21 / 79 as start/stop numbers for cman and you don't have any Provides or Required-* section for it (at least in version cman-2.0.115-1.el5_4.9)</div>
<div><br></div><div>In current F12 (cman-3.0.7-1.fc12) you have again 21 / 79 as start / stop numbers and:</div><div><div>### BEGIN INIT INFO</div><div># Provides: cman</div><div># Required-Start: $network $time</div>
<div># Required-Stop: $network $time</div><div># Default-Start:</div><div># Default-Stop:</div><div># Short-Description: Starts and stops cman</div><div># Description: Starts and stops the Cluster Manager set of daemons</div>
<div>### END INIT INFO</div></div><div><br></div><div>So if drbd starts in 20 it is ok already ootb.</div><div>Probably there is only a problem of latencies... drbd start ends and cman suddenly starts, but drbd is not yet at Primary UpToDate level....</div>
<div>I have not here the config I used at that time, but I seem to remember in F11 and F12 I had a similar problem and I solved it changing cman script adding at the beginning of the start step a sort of drbd status check,</div>
<div>so that if it didn't reach a status acceptable for drbd (st Primary for this node and ds UpToDate for this node) in N attempts, cman didn't started, preventing problems with VMs that had their storage on drbd replicated pools...</div>
<div><br></div><div>HIH,</div><div>Gianluca</div>