From: Patrick Caulfield <pcaulfie@redhat.com>
To: Boris Ostrovsky <baostr@gmail.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM2 and OCFS2
Date: Wed, 13 Dec 2006 09:00:11 +0000 [thread overview]
Message-ID: <457FC11B.3090105@redhat.com> (raw)
In-Reply-To: <fd8dc0d20612120946l1fe841fvbc284b28453ff270@mail.gmail.com>
Boris Ostrovsky wrote:
> (Resending with cc: fixed)
>
>> 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 if I can guarantee that other nodes will not access LVM metadata
> (i.e. they will not issue any LVM command) until I run 'vgchange -ay'
> on them? The only access that those other nodes will have to volumes
> is that they will have some of them mounted.
>
> Is this still dangerous? My (limited) understanding of metadata is
> that it is stored in the first few blocks of a disk (or striped, if
> necessary) and is cached in lvm.cache. vgchange will sync disk and
> cache, so it should be OK, right?
Yes, that should work.
Just be VERY, VERY careful!
patrick
next prev parent reply other threads:[~2006-12-13 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fd8dc0d20612120940w2c6c4c07m51de6ea8337973d9@mail.gmail.com>
2006-12-12 17:46 ` [linux-lvm] LVM2 and OCFS2 Boris Ostrovsky
2006-12-13 9:00 ` Patrick Caulfield [this message]
2006-12-09 14:19 Michael Lessard
2006-12-11 10:13 ` Patrick Caulfield
2006-12-11 11:35 ` Morten Torstensen
2006-12-12 4:52 ` Nate Carlson
2006-12-12 0:11 ` Michael Lessard
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=457FC11B.3090105@redhat.com \
--to=pcaulfie@redhat.com \
--cc=baostr@gmail.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).