On Tue, Mar 6, 2012 at 3:53 AM, Florian Haas flor...@hastexo.com wrote:
On Sat, Mar 3, 2012 at 8:14 PM, Florian Haas flor...@hastexo.com wrote:
In other words, interleave=true is actually the reasonable thing to
set on all clone instances by default, and I believe the pengine
actually does use
Hi,
On Wed, Mar 07, 2012 at 07:52:16PM -0500, William Seligman wrote:
On 3/5/12 11:55 AM, William Seligman wrote:
On 3/3/12 3:30 PM, William Seligman wrote:
On 3/3/12 2:14 PM, Florian Haas wrote:
On Sat, Mar 3, 2012 at 6:55 PM, William Seligman
selig...@nevis.columbia.edu wrote:
On
On 3/5/12 11:55 AM, William Seligman wrote:
On 3/3/12 3:30 PM, William Seligman wrote:
On 3/3/12 2:14 PM, Florian Haas wrote:
On Sat, Mar 3, 2012 at 6:55 PM, William Seligman
selig...@nevis.columbia.edu wrote:
On 3/3/12 12:03 PM, emmanuel segura wrote:
are you sure the exportfs agent can
On Sat, Mar 3, 2012 at 8:14 PM, Florian Haas flor...@hastexo.com wrote:
In other words, interleave=true is actually the reasonable thing to
set on all clone instances by default, and I believe the pengine
actually does use a default of interleave=true on defined clone sets
since some 1.1.x
On 3/3/12 3:30 PM, William Seligman wrote:
On 3/3/12 2:14 PM, Florian Haas wrote:
On Sat, Mar 3, 2012 at 6:55 PM, William Seligman
selig...@nevis.columbia.edu wrote:
On 3/3/12 12:03 PM, emmanuel segura wrote:
are you sure the exportfs agent can be use it with clone active/active?
a) I've
On Sat, Mar 3, 2012 at 9:30 PM, William Seligman
selig...@nevis.columbia.edu wrote:
In other words, interleave=true is actually the reasonable thing to
set on all clone instances by default, and I believe the pengine
actually does use a default of interleave=true on defined clone sets
since
are you sure the exportfs agent can be use it with clone active/active?
Il giorno 03 marzo 2012 00:12, William Seligman selig...@nevis.columbia.edu
ha scritto:
One step forward, two steps back.
I'm working on a two-node primary-primary cluster. I'm debugging problems
I have
with the
On 3/3/12 12:03 PM, emmanuel segura wrote:
are you sure the exportfs agent can be use it with clone active/active?
a) I've been through the script. If there's some problem associated with
it being cloned, I haven't seen it. (It can't handle
globally-unique=true, but I didn't turn that on.)
On Sat, Mar 3, 2012 at 6:55 PM, William Seligman
selig...@nevis.columbia.edu wrote:
On 3/3/12 12:03 PM, emmanuel segura wrote:
are you sure the exportfs agent can be use it with clone active/active?
a) I've been through the script. If there's some problem associated with it
being cloned, I
On 3/3/12 2:14 PM, Florian Haas wrote:
On Sat, Mar 3, 2012 at 6:55 PM, William Seligman
selig...@nevis.columbia.edu wrote:
On 3/3/12 12:03 PM, emmanuel segura wrote:
are you sure the exportfs agent can be use it with clone active/active?
a) I've been through the script. If there's some
One step forward, two steps back.
I'm working on a two-node primary-primary cluster. I'm debugging problems I have
with the ocf:heartbeat:exportfs resource. For some reason, pacemaker sometimes
appears to ignore ordering I put on the resources.
Florian Haas recommended pastebin in another
Darn it, forgot versions:
Redhat Linux 6.2 (kernel 2.6.32)
cman-3.0.12.1
corosync-1.4.1
pacemaker-1.1.6
On 3/2/12 6:12 PM, William Seligman wrote:
One step forward, two steps back.
I'm working on a two-node primary-primary cluster. I'm debugging problems I
have
with the
12 matches
Mail list logo
