<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Pavlos Parissis wrote:
<blockquote
cite="mid:AANLkTikmxP+xbxLyGY_1VEtGL+ykGrcm5YKCY7+dSJgf@mail.gmail.com"
type="cite">
<pre wrap="">On 13 October 2010 09:48, Dan Frincu <a class="moz-txt-link-rfc2396E" href="mailto:dfrincu@streamwide.ro"><dfrincu@streamwide.ro></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
I've noticed the same type of behavior, however in a different context, my
setup includes 3 drbd devices and a group of resources, all have to run on
the same node and move together to other nodes. My issue was with the first
resource that required access to a drbd device, which was the
ocf:heartbeat:Filesystem RA trying to do a mount and failing.
The reason, it was trying to do the mount of the drbd device before the drbd
device had finished migrating to primary state. Same as you, I introduced a
start-delay, but on the start action. This proved to be of no use as the
behavior persisted, even with an increased start-delay. However, it only
happened when performing a fail-back operation, during fail-over, everything
was ok, during fail-back, error.
The fix I've made was to remove any start-delay and to add group collocation
constraints to all ms_drbd resources. Before that I only had one collocation
constraint for the drbd device being promoted last.
I hope this helps.
</pre>
</blockquote>
<pre wrap=""><!---->
I am glad that somebody else experienced the same issue:)
On my mail I was talking about the monitor action which was failing,
but the behavior you described happened on my system on the same
setup, drbd and fs resource.It also happened on the application
resource, the start was too fast and the FS was not mounted (yet) when
the action start fired for the application resource. A delay on start
function of the resource agent of the application fixed my issue.
In my setup I have all the necessary constraints to avoid this, at
least this is what I believe so:-)
Cheers,
Pavlos
</pre>
</blockquote>