Hi Joel,
As CLVM is to be configured along with the cluster-suite and you stated
"[...] that [CLVM] uses a different cluster technology than ocfs2 does,
and as such the two cluster stacks may conflict when a node goes down."
What are the common solutions to this problem ?
Thanks,
Ionel
Joel Becker wrote:
On Tue, Jul 08, 2008 at 05:36:48PM +0100, Pedro Figueira wrote:
Why do you consider the LVM2 not cluster safe? Is it just because you should
not (can't) modify any LVM configuration with the volume groups activated in
more than one server?
Not only can you not modify it, there are also configurations
where the LVM2 code will do modifications behind your back - and the
other nodes don't know about it. For example, dm-mirror keeps track of
changes that have only hit one copy so far. Another node might read the
un-updated copy before it has been updated by the writing node. That's
not safe.
We consider data integrity of paramount importance. Trying to
configure LVM2 (non-clustered) to make sure nothing will change is not
trivial. We won't recommend it, knowing that it just takes one admin
who isn't paying attention to wipe out your entire volume.
Joel
--
Ionel GARDAIS
System-Network Engineer
begin:vcard
fn:Ionel GARDAIS
n:GARDAIS;Ionel
org:Tech'Advantage;IT
adr:;;1 Rue Isabey;Rueil Malmaison;FR;92500;FR
email;internet:[EMAIL PROTECTED]
tel;work:+33(0)147088131
tel;fax:+33(0)147088065
x-mozilla-html:FALSE
url:http://www.tech-advantage.com
version:2.1
end:vcard
_______________________________________________
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users
