From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Two computers with one shared array?
Date: Tue, 7 Aug 2001 14:51:21 +0100 [thread overview]
Message-ID: <20010807145121.D677@tykepenguin.com> (raw)
In-Reply-To: <20010807153154.P495@hogia.net>; from sa@hogia.net on Tue, Aug 07, 2001 at 03:31:54PM +0200
On Tue, Aug 07, 2001 at 03:31:54PM +0200, Sebastian Andersson wrote:
> I've got two computers connected to a JBOD array.
> On it I've got 3 VGs and a bunch of free disks.
> I'd like to use 2 of the VGs on one of the computers and the
> other VG on the other computer.
>
> Should I still vgscan on both computers at startup and then
> vgchange -a y VG1 VG2 on the first computer and
> vgchange -a y VG3 on the other computer?
>
> Is it safe to vgchange -a n on both computers or should
> I only vgchange -a n VGx ?
>
> Can I change the LVGs in a VG or do I need to inactivate everything on
> the other computer while I do this and then vgscan after I'm done?
First advice: BE VERY CAREFUL!
vgchange simply affects the kernel's view of the metadata so you can do that any
time you like on either node. similarly vgscan should also be OK to run at
system startup because it only reads metadata and updates the local cache files.
If you need to do any changes you MUST vgchange -an on one machine before
changing metatdata on the other. THEN do a vgscan before vgchange -ay.
So, yes the startup sequence of vgscan/vgchange is the same as for a single node
system but *ANY* metadata changes must be done from one node while the other has
no LVM data in kernel.
I feel a FAQ entry coming on!
patrick
P.S. Of course, if you actually want to share the data on the disks you could
use GFS!
prev parent reply other threads:[~2001-08-07 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 13:31 [linux-lvm] Two computers with one shared array? Sebastian Andersson
2001-08-07 13:42 ` Neil Macvicar
2001-08-07 13:52 ` Patrick Caulfield
2001-08-07 13:51 ` Patrick Caulfield [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=20010807145121.D677@tykepenguin.com \
--to=caulfield@sistina.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.