Linux LVM users
 help / color / mirror / Atom feed
From: Jesse Sipprell <jss@evcom.net>
To: Jos Visser <josv@osp.nl>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] LVM in shared parallel SCSI environment
Date: Tue, 14 Nov 2000 09:38:55 -0500	[thread overview]
Message-ID: <20001114093855.A21984@kevorkian.evcom.net> (raw)
In-Reply-To: <20001114074425.Z370@jadzia.josv.com>; from josv@osp.nl on Tue, Nov 14, 2000 at 07:44:25AM +0100

On Tue, Nov 14, 2000 at 07:44:25AM +0100, Jos Visser wrote:
> Hi Jesse,
> 
> Let's see if I get this right: You have an LVM configuration on a shared
> SCSI disk set. I understand from your description that you have some
> VG's active on more than one node at a time. Is this right? If so, I
> wonder if it's supported (others are better equiped to determine this
> than I am). However, most volume managers on other Unix platforms do not
> allow this. 
> 
> As far as I know the vgchange inactive/active bounce is the only thing
> that will refresh the metadata. 
> 
> However, if you have the VG truly active on more than one node (if
> that's possible), you have a recipe for disaster! What if you by mistake
> change the VG (e.g. adding an LV) from one node, and then perform a
> similar action from another node? I would not be surprised if there
> would be corruptions, oopses and panics all over the place.

You are correct, sir. ;)  It is exceedingly important that each node's view of
the LVM metadata be consistant.  I understand that the addition of LVM
clustering features (including this issue and others) is currently in the
works.

In the mean time, I'll just have to do things the old fashioned way.  I'll put
a procedure in place that any LVM changes done from a particular node require
the bouncing of VGs on all other attached nodes.  Fortunately, after initial
cluster setup, manipulation of LVs won't really be performed on a routine
basis.

-- 
Jesse Sipprell
Technical Operations Director
Evolution Communications, Inc.
800.496.4736

* Finger jss@evcom.net for my PGP Public Key *

  reply	other threads:[~2000-11-14 14:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-11 13:46 [linux-lvm] LVM in shared parallel SCSI environment Jesse Sipprell
2000-11-14  6:44 ` Jos Visser
2000-11-14 14:38   ` Jesse Sipprell [this message]
2000-11-14 16:09     ` Paul Jakma
2000-11-14 19:29       ` Jesse Sipprell
     [not found]         ` <200011142115.eAELFHV11698@webber.adilger.net>
2000-11-14 22:03           ` Jesse Sipprell
2000-11-14 22:40             ` Andreas Dilger
2000-11-15  7:04         ` Jos Visser
2000-11-21 13:44           ` Matthew O'Keefe
2000-11-21 18:01             ` John DeFranco
2000-11-21 22:25             ` Jos Visser
2000-11-22  0:42               ` Matthew O'Keefe
2000-11-22 11:40                 ` Heinz J. Mauelshagen

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=20001114093855.A21984@kevorkian.evcom.net \
    --to=jss@evcom.net \
    --cc=josv@osp.nl \
    --cc=linux-lvm@msede.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