From: Patrick Caulfield <pcaulfie@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM2 and OCFS2
Date: Mon, 11 Dec 2006 10:13:20 +0000 [thread overview]
Message-ID: <457D2F40.7060708@redhat.com> (raw)
In-Reply-To: <c5530b840612090619v2f807944h361a5dc163cb69c4@mail.gmail.com>
Michael Lessard wrote:
> Hi Everyboy !
>
> I read that LVM2 is not cluster aware (specially with OCFS2) from
> different post on internet forum... If it's true, could someone could
> confirm this information and point me where i can find this affirmation
> in documentention ?
>
> I do some test with OCFS2 on LVM2 and it's seems to run correctly , so
> i have some interrogation about this fact !
It's true that lvm is not cluster-aware. What that means is that if you update the volume groups on one node then the other nodes in
the cluster will not see the changes and you could end up with the block devices on the machines dangerously out of sync.
What you tried (it seems to me) is just created LVM volumes and run OCFS2 on them. that /will/ work provided you never change the
volume groups!
To get clustered LVM you need to use clvm (RPM package lvm2-cluster) which synchronises LVM metadata updates across the cluster.
This only works with Red Hat cluster suite though - you would need you write your own cluster management plugin for OCFS2 if you
wanted to use that (hard, but not impossible). Of course, RHCS does offer GFS as the cluster filesystem, if that's what you really need!
--
patrick
next prev parent reply other threads:[~2006-12-11 10:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 14:19 [linux-lvm] LVM2 and OCFS2 Michael Lessard
2006-12-11 10:13 ` Patrick Caulfield [this message]
2006-12-11 11:35 ` Morten Torstensen
2006-12-12 4:52 ` Nate Carlson
2006-12-12 0:11 ` Michael Lessard
[not found] <fd8dc0d20612120940w2c6c4c07m51de6ea8337973d9@mail.gmail.com>
2006-12-12 17:46 ` Boris Ostrovsky
2006-12-13 9:00 ` Patrick Caulfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=457D2F40.7060708@redhat.com \
--to=pcaulfie@redhat.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).