Here is the output from 'service drbd status' on the node where the
slave does not start. It appears that it is started but "unconfigured"
# service drbd status
drbd driver loaded OK; device status:
version: 0.7.25 (api:79/proto:74)
GIT-hash: 3a9c7c136a9af8df921b3628129dafbe212ace9f build by
[EMAIL PROTECTED], 2008-02-04 09:05:54
0: cs:Unconfigured
After I issue the 'service drbd start' it looks like this;
# service drbd status
drbd driver loaded OK; device status:
version: 0.7.25 (api:79/proto:74)
GIT-hash: 3a9c7c136a9af8df921b3628129dafbe212ace9f build by
[EMAIL PROTECTED], 2008-02-04 09:05:54
0: cs:Connected st:Secondary/Primary ld:Consistent
ns:0 nr:16384 dw:16384 dr:0 al:0 bm:7 lo:0 pe:0 ua:0 ap:0
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:linux-ha-
> [EMAIL PROTECTED] On Behalf Of Damon Estep
> Sent: Tuesday, February 19, 2008 9:02 AM
> To: General Linux-HA mailing list
> Subject: RE: [Linux-HA] drbd heartbeat v2
>
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:linux-ha-
> > [EMAIL PROTECTED] On Behalf Of Dominik Klein
> > Sent: Tuesday, February 19, 2008 1:52 AM
> > To: General Linux-HA mailing list
> > Subject: Re: [Linux-HA] drbd heartbeat v2
> >
> > Damon Estep wrote:
> > > On this page: http://www.linux-ha.org/DRBD/HowTov2 is this
comment:
> > > "drbd must not be started by init"
> >
> > Well, you do not have to start drbd by init. But it shouldn't harm
if
> > you do.
> [Damon Estep]
>
> I have attached the config. 'before' is with everything running,
> 'after'
> is after the reset with no drbd slave running. Status section
included.
> I have also included the syslog from the point where the reset node is
> shown online again by pengine.
>
> The issue is that the drbd ofc/heartbeat RA not starting drbd after
> reset of the active node. CentOS 4.6, Heartbeat 2.1.3, DRBD 0.7.25
> (also tried DRBD 8.0.10).
>
> If I start DRBD on each node it will run and failover with no issues.
> The problem is when the active node is reset (power cycle) it comes
> back up and the slave role of the drbd master/slave resource agent
will
> not start unless I manually issue a 'service drbd start', after drbd
is
> started the RA can start the slave role.
>
> This looks like a bug because the drbd slave starts with no other
> change sother than to start drbd with 'service drbd start' which
should
> be handled by the RA (timing issue?).
>
> The output from crm_verify -L after the reset node comes back up is;
>
> crm_verify[19814]: 2008/02/19_08:46:57 WARN: unpack_rsc_op: Processing
> failed op drbd0:1_start_0 on cn2-inverness-co: Error
> crm_verify[19814]: 2008/02/19_08:46:57 WARN: unpack_rsc_op:
> Compatability handling for failed op drbd0:1_start_0 on cn2-inverness-
> co
> crm_verify[19814]: 2008/02/19_08:46:57 WARN: native_color: Resource
> drbd0:1 cannot run anywhere
> Warnings found during check: config may not be valid
>
> Thank you,
>
> Damon
>
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
