From: Austin Gonyou <austin@coremetrics.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] has anyone used LVM in a HA cluster?
Date: Fri May 10 17:51:01 2002 [thread overview]
Message-ID: <1021071171.17474.44.camel@UberGeek> (raw)
In-Reply-To: <20020510072608.GA1001@tykepenguin.com>
[-- Attachment #1: Type: text/plain, Size: 2355 bytes --]
From what I understand you *can* mount the LVM volumes on multiple hosts
at the same time, but you should be *readonly* on the hosts which do not
*own* the data on the disks. You could then *remount* the volume on the
target failover host.
The only draw back is you will need to have monitoring, in the end
anyway, that will allow you to see:
1. What hosts have what volumes mounted
2. and in what mode(ro/rw?)
Also, you would need to use a filesystem that supports:
1. multiple hosts mounting it
2. filesystem 'remount' option
Talk to the guys on the Linux FailSafe list, they might be able to help
point you as well.
On Fri, 2002-05-10 at 02:26, Patrick Caulfield wrote:
> On Thu, May 09, 2002 at 09:54:40AM -0700, Au, Richard wrote:
> > Hi,
> >
> > I'm wondering if anyone has used LVM in a high-availibility
> cluster
> > where two servers are connected to shared storage (the physical
> > volumes). If so, which cluster solution did you use? Will there
> be
> > problems if the logical volumes are visable to both servers, even
> if
> > only one of them has them mounted? Thanks!
>
> Provided you're either using GFS as the file system or being VERY
> careful to
> mount the filesystem on only one node at a time you can do this.
>
> The key is just to be VERY careful. If you need to do any LVM
> commands you MUST
>
> umount filesystems on all other nodes
> vgchange -an on all other nodes
>
> do the LVM metadata changes
>
> vgscan on all nodes
> vgchange -ay on all nodes.
>
> The safe thing to do is to have only one node have the LVM commands
> available to
> it (apart from vgscan & vgchange) and be VERY careful.
>
> I'll say that again: Be VERY careful !
>
> patrick
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin@coremetrics.com
"One ought never to turn one's back on a threatened danger and
try to run away from it. If you do that, you will double the danger.
But if you meet it promptly and without flinching, you will
reduce the danger by half."
Sir Winston Churchill
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-05-10 17:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 11:53 [linux-lvm] has anyone used LVM in a HA cluster? Au, Richard
2002-05-09 12:14 ` Tim
2002-05-09 14:38 ` Chad Walstrom
2002-05-09 14:46 ` Goetz Bock
2002-07-13 7:12 ` Wichert Akkerman
2002-05-10 2:24 ` Patrick Caulfield
2002-05-10 17:51 ` Austin Gonyou [this message]
2002-05-10 19:45 ` Steven Lembark
2002-05-11 14:26 ` Luca Berra
2002-05-13 4:15 ` Michael Lausch
2002-05-13 6:54 ` Luca Berra
2002-05-13 7:33 ` Tim
2002-05-13 10:59 ` Michael Lausch
2002-05-13 11:23 ` Steven Lembark
2002-05-13 11:28 ` Tim
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=1021071171.17474.44.camel@UberGeek \
--to=austin@coremetrics.com \
--cc=linux-lvm@sistina.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.