From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Volume Groups and Clusters
Date: Sun, 26 Feb 2006 14:42:27 +0100 [thread overview]
Message-ID: <20060226134227.GC23655@redhat.com> (raw)
In-Reply-To: <1140808929.6609.8.camel@fritzdesk.potsdam.edu>
On Fri, Feb 24, 2006 at 02:22:08PM -0500, Jeff Hardy wrote:
> I played around with this kind of setup for awhile, and found that there
> was no need to vgchange -an on the "Other nodes" when I was making
> changes on the "Admin node." I was also able to make volume changes on
> two Admin nodes at the same time. I figured I was probably just
> extremely lucky to win some extremely dangerous race conditions, so I
> wouldn't do it in production. I assume the cluster extensions to LVM
> (CLVM) are what allow multiple Admin actions on multiple Admin nodes?
Yes.
Heinz
>
> Anyway, just some friendly advice: follow the docs :)
>
>
> On Wed, 2006-02-22 at 08:27 -0500, Joshua ChaitinPollak wrote:
> > On Feb 22, 2006, at 8:12 AM, Patrick Caulfield wrote:
> >
> > > Joshua ChaitinPollak wrote:
> > >>
> > >> On Feb 22, 2006, at 3:49 AM, Heinz Mauelshagen wrote:
> > >>
> > >>> On Tue, Feb 21, 2006 at 04:22:10PM -0500, Joshua ChaitinPollak
> > >>> wrote:
> > >>>> Hello, I found this mention of sharing Volume Groups across
> > >>>> Clusters
> > >>>> on the LVM howto:
> > >>>>
> > >>>> http://www.tldp.org/HOWTO/LVM-HOWTO/sharinglvm1.html
> > >>>>
> > >>>> Am I right in assuming that this means you can have a single volume
> > >>>> group active on multiple nodes in a cluster, provided that you
> > >>>> doing
> > >>>> mount the same logical volume on more than one node at a time?
> > >>>
> > >>> Yes, you assume right *but* you need a cluster filesystem (eg, GFS)
> > >>> as well to be able to mount shared logical volumes on multiple nodes
> > >>> at once or you mess up the data.
> > >>
> > >> Right, but I don't need GFS if I'm only going to mount the file
> > >> system
> > >> on one machine at a time, right?
> > >
> > > No, just a lot of care and discipline :)
> >
> > Great! And, my co-workers keep telling me, "You lack discipline!"
> >
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Red Hat GmbH
Consulting Development Engineer Am Sonnenhang 11
Cluster and Storage Development 56242 Marienrachdorf
Germany
Mauelshagen@RedHat.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2006-02-26 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 21:22 [linux-lvm] Volume Groups and Clusters Joshua ChaitinPollak
2006-02-22 8:49 ` Heinz Mauelshagen
2006-02-22 12:52 ` Joshua ChaitinPollak
2006-02-22 13:12 ` Patrick Caulfield
2006-02-22 13:27 ` Joshua ChaitinPollak
2006-02-24 19:22 ` Jeff Hardy
2006-02-26 13:42 ` Heinz Mauelshagen [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=20060226134227.GC23655@redhat.com \
--to=mauelshagen@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.