From: Jonathan Tripathy <jonnyt@abpni.co.uk>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] SAN
Date: Fri, 22 Apr 2011 17:42:25 +0100 [thread overview]
Message-ID: <4DB1AFF1.7000800@abpni.co.uk> (raw)
In-Reply-To: <alpine.LRH.2.00.1104221236420.8342@bmsred.bmsi.com>
On 22/04/2011 17:38, Stuart D. Gathman wrote:
> On Fri, 22 Apr 2011, Jonathan Tripathy wrote:
>
>> What is the best way to deploy LVM in such a way that multiple
>> servers could access the LVs? Really what I'm looking for is a
>> "common VG" for all of our servers. Note though that only one server
>> will actually access each LV, however it would be cool if another
>> server could make a snapshot to perform an rsync backup.
>
> This is what cluster LVM is for. It provides a locking mechanism to
> avoid conflicting changes to LVM metadata.
>
I'm a little confused on where CLVM fits into the "big picture". Let's
say I have one SAN server, and 10 Xen Servers. Where do I install CLVM?
next prev parent reply other threads:[~2011-04-22 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 16:28 [linux-lvm] SAN Jonathan Tripathy
2011-04-22 16:38 ` Stuart D. Gathman
2011-04-22 16:42 ` Jonathan Tripathy [this message]
2011-04-22 17:22 ` Jonathan Tripathy
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=4DB1AFF1.7000800@abpni.co.uk \
--to=jonnyt@abpni.co.uk \
--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).