[linux-lvm] Two computers with one shared array?

[linux-lvm] Two computers with one shared array?

[Sebastian Andersson]

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?

Regards,
/Sebastian
-- 
                             .oooO o,o Oooo.           Sex,
                             (   ) \_/ (   )      (o_   Drugs
"Life is not fair, but root   \ (  /|\  ) / (o_   //\    and
password helps!" -- The BOFH   \_)     (_/  (/)_  V_/_    UNIX.

Re: [linux-lvm] Two computers with one shared array?

[Neil Macvicar]

hmm.. on HP, the LVM system lets you exclusively activate a VG.. does Linux
LVM allow you to do this ?

----- Original Message -----
From: "Sebastian Andersson" <sa@hogia.net>
To: <linux-lvm@sistina.com>
Sent: Tuesday, August 07, 2001 2:31 PM
Subject: [linux-lvm] Two computers with one shared array?


> 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?
>
> Regards,
> /Sebastian
> --
>                              .oooO o,o Oooo.           Sex,
>                              (   ) \_/ (   )      (o_   Drugs
> "Life is not fair, but root   \ (  /|\  ) / (o_   //\    and
> password helps!" -- The BOFH   \_)     (_/  (/)_  V_/_    UNIX.
> _______________________________________________
> 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

Re: [linux-lvm] Two computers with one shared array?

[Patrick Caulfield]

On Tue, Aug 07, 2001 at 02:42:25PM +0100, Neil Macvicar wrote:
> hmm.. on HP, the LVM system lets you exclusively activate a VG.. does Linux
> LVM allow you to do this ?

Not yet - but we're working on it!

patrick

Re: [linux-lvm] Two computers with one shared array?

[Patrick Caulfield]

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!