linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Lamont R. Peterson" <peregrine@openbrainstem.net>
To: LVM <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Running LVM on shared LUNs
Date: Tue, 8 Aug 2006 00:50:36 -0600	[thread overview]
Message-ID: <200608080050.42004.peregrine@openbrainstem.net> (raw)
In-Reply-To: <1154987972.16651.28.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2355 bytes --]

On Monday 07 August 2006 03:59pm, Joshua Aune wrote:
> I have two systems that are connected to a SAN.  The SAN is exporting
> the same 4 luns to each system (/dev/sd[b,c,d,e]).  Under normal
> operation system1 will combine sdb with sdc into a vg and system2 will
> combine sdd with sde into a vg with both vgs consisting of one large lv
> and one small lv.  After the system is configured there will be no
> modifications made to the LVM configuration.  LVM is configured on one
> node and then copied over to the second node.
>
> The million dollar question is, can system1 and system2 simultaneously
> have both of the VGs active without hosing any data?

As I understand it, only if you are using a filesystem that supports clustered 
operations, like GFS.

> I am not trying to have the same filesystem mounted simultaneously, just
> have the LVs available simultaneously for failover needs

In that case, as long as you have some heartbeat or something that lets you 
know when the one system needs to take over the other's PVs.  The trick here 
is that if you lose your network connection, but the box is still accessing 
data on the LUNs, that could become problematic.  Maybe a tiny little shared 
GFS thing would allow your boxes a place to write some status info (a 
custom "heartbeat", if you will) so that a network disconnect or other issue 
won't cause false alarms.

Probably best to just use GFS.

> I know that this sort of config can be done with the GFS pool volume
> manger but I have been told that many other VMs don't support this
> behavior....

/me shrugs

Not sure about that as I don't have any SAN to play with :( .  Never tried it.
-- 
Lamont R. Peterson <peregrine@OpenBrainstem.net>
Founder [ http://blog.OpenBrainstem.net/peregrine/ ]
GPG Key fingerprint: 0E35 93C5 4249 49F0 EC7B  4DDD BE46 4732 6460 CCB5
  ___                   ____            _           _
 / _ \ _ __   ___ _ __ | __ ) _ __ __ _(_)_ __  ___| |_ ___ _ __ ___
| | | | '_ \ / _ \ '_ \|  _ \| '__/ _` | | '_ \/ __| __/ _ \ '_ ` _ \
| |_| | |_) |  __/ | | | |_) | | | (_| | | | | \__ \ ||  __/ | | | | |
 \___/| .__/ \___|_| |_|____/|_|  \__,_|_|_| |_|___/\__\___|_| |_| |_|
      |_|               Intelligent Open Source Software Engineering
                              [ http://www.OpenBrainstem.net/ ]

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-08-08  6:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 21:59 [linux-lvm] Running LVM on shared lun's Joshua Aune
2006-08-08  6:50 ` Lamont R. Peterson [this message]
2006-08-08  8:13   ` [linux-lvm] Running LVM on shared LUNs Christian.Rohrmeier
2006-08-08 15:01   ` Joshua Aune
2006-08-08 16:23 ` [linux-lvm] Running LVM on shared lun's David Chan
2006-08-15  9:55   ` Luca Berra

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=200608080050.42004.peregrine@openbrainstem.net \
    --to=peregrine@openbrainstem.net \
    --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).