From: Jesse Sipprell <jss@evcom.net>
To: Paul Jakma <paulj@itg.ie>
Cc: Jos Visser <josv@osp.nl>, linux-lvm@msede.com
Subject: Re: [linux-lvm] LVM in shared parallel SCSI environment
Date: Tue, 14 Nov 2000 14:29:02 -0500 [thread overview]
Message-ID: <20001114142902.A25706@kevorkian.evcom.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0011141608080.21566-100000@rossi.itg.ie>; from paulj@itg.ie on Tue, Nov 14, 2000 at 04:09:47PM +0000
On Tue, Nov 14, 2000 at 04:09:47PM +0000, Paul Jakma wrote:
> On Tue, 14 Nov 2000, Jesse Sipprell wrote:
>
> > 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.
>
> and so what do you do with these LV's? The filesystem/application you
> run on them has to be aware of the shared-access nature of the
> device.. so that rules out all but GFS - which IIRC already has some
> LVM like features.
Actually, it's entirely possible to run a non-shared-media-aware filesystem as
long as no more than one cluster node has a given file system mounted at a
time.
To illustrate:
|-------- VG --------|
||====== LV0 =======||
|| (ext2) || --> Mounted on Cluster Node 1
||==================||
||====== LV1 =======||
|| (ext2) || --> Mounted on Cluster Node 2
||==================||
||====== LV2 =======||
|| (ext2) || --> Mounted on Cluster Node 3
||==================||
||====== LV3 =======||
|| (ext2) || --> Mounted on Cluster Node 4
||==================||
| |
| Free Space in VG |
| |
|====================|
Because none of the cluster nodes are attempting to share access to the actual
blocks where each filesystem is stored, there are no concurrency issues.
One can use the benefits of LVM to unmount LV0's fs on Cluster Node 1, resize
the LV, resize the fs and remount. Now, Cluster Node's 2, 3 and 4 need to
have their in-core LVM metadata updated in order to see the new size of LV0.
Once this is done via the vgchange bounce, everything is consistant.
--
Jesse Sipprell
Technical Operations Director
Evolution Communications, Inc.
800.496.4736
* Finger jss@evcom.net for my PGP Public Key *
next prev parent reply other threads:[~2000-11-14 19:29 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
2000-11-14 16:09 ` Paul Jakma
2000-11-14 19:29 ` Jesse Sipprell [this message]
[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=20001114142902.A25706@kevorkian.evcom.net \
--to=jss@evcom.net \
--cc=josv@osp.nl \
--cc=linux-lvm@msede.com \
--cc=paulj@itg.ie \
/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