All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Wysochanski <dwysocha@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Sharing volumes via SAN?
Date: Tue, 10 Apr 2007 10:40:57 -0400	[thread overview]
Message-ID: <1176216057.4380.2.camel@linux-cxyg> (raw)
In-Reply-To: <20070409182959.GA7163@pri.dmz.gmi.com>

On Mon, 2007-04-09 at 11:29 -0700, Adam D. Morley wrote:
> Hi,
> 
> I'd like to share LVM volumes hosted on a SAN between two systems.  I do
> not want to mount at the same time (ie: GFS), but rather I just want
> to be able to swap them between hosts.  I'm assuming this is possible
> now by simply assigning SAN LUNs to both systems, but I don't see
> much talk of about a piece of LVM that handles knowing which host
> "owns" a given LV.
> 
> Background: In Solaris, when using Sun's VM, one can create a shared
> diskset which is seen by two hosts, but only one can do IO against the
> volumes at a given time.  Solaris also implements a forcible take
> mechanism which allows the passive host to take the volumes from the
> active host, panicing the active host out.  Regular takes are also
> implemented, to allow the volumes to migrate between hosts if first
> released by the active host.
> 
> It doesn't seem like LVM does this out of the box, probably because it
> lacks a built-in lock manager.  If it does, could someone point me to a
> resource that shows how it works?
> 

See Q#6:
http://sources.redhat.com/lvm2/wiki/FrequentlyAskedQuestions



> In the event LVM doesn't do this, is this something that CLVM will do?
> Was there ever a version of CLVM for the 2.4.x kernel series?

> Thanks!
> 

      reply	other threads:[~2007-04-10 14:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 18:29 [linux-lvm] Sharing volumes via SAN? Adam D. Morley
2007-04-10 14:40 ` Dave Wysochanski [this message]

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=1176216057.4380.2.camel@linux-cxyg \
    --to=dwysocha@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 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.