All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Robinson <zxvdr.au@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm on a share environnement (SAN inside)
Date: Fri, 28 Sep 2007 17:12:59 +1000	[thread overview]
Message-ID: <46FCA97B.9000109@gmail.com> (raw)
In-Reply-To: <290F03E9-E521-4E3A-824F-8C4DCBD8341B@ensil.unilim.fr>

hubert chomette wrote:
> the two machine use the same lun, on this lun, there is one vg with a 
> logical volume by virtual machine (10 virtual machine).
> The idea is if one xen is down, the other can launch the virtual machine 
> ad continu service.

So its a high-availability cluster...

>>> - Is it possible to allow LVM metadata modification by only one server?
>>> - should I use clvm instead?

The link below describes what can happen.

http://www.tldp.org/HOWTO/LVM-HOWTO/sharinglvm1.html

It sounds like you should be using CLVM. CLVM extends LVM2 to provide 
cluster-wide management of Logical Volumes. LVM and CLVM are essentially 
the same thing, but CLVM is cluster aware, LVM is not.

Alasdair has some presentations which describe CLVM in detail here:

http://people.redhat.com/agk/talks/CLVM-UKUUG2007/

>>> - Is it possible to migrate lvm to clvm without any data lost?

There's no migration involved, you just need to enable cluster locking 
for the shared volume group.

eg: vgchange -c y VolumeGroupName

--Dave

  parent reply	other threads:[~2007-09-28  7:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 13:50 [linux-lvm] lvm on a share environnement (SAN inside) hubert chomette
2007-09-27 17:36 ` Chris Cox
2007-09-27 19:01   ` hubert chomette
2007-09-27 21:12     ` Chris Cox
2007-09-28  0:18       ` hubert chomette
2007-09-28 15:50         ` Chris Cox
2007-09-28  7:12     ` David Robinson [this message]
2007-10-02 10:11       ` hubert chomette

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=46FCA97B.9000109@gmail.com \
    --to=zxvdr.au@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.