From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Cuncurrent access to a vg from two hosts
Date: Fri Nov 14 08:13:02 2003 [thread overview]
Message-ID: <20031114151201.H28265@sistina.com> (raw)
In-Reply-To: <20031113183745.GA9193@gmx.de>; from wodecki@gmx.de on Thu, Nov 13, 2003 at 07:37:45PM +0100
On Thu, Nov 13, 2003 at 07:37:45PM +0100, Wiktor Wodecki wrote:
> Hello,
>
> I'm curious if lvm1 allows me to access the same volume group from to
> different machines (of course not accessing the same lv's in this vg). I
> have two machines connected to a storage array, that's why I ask. Is the
> filesystem operations on the LV affecting the VG so that this could lead
> to inconsistencies?
You can access different LVs in the same SAN shared VG presumably you
make changes to the VG (eg: create, resize LVs) when it is active (vgchange -ay)
on one of them only. After done with the changes, run vgscan and "vgchange -ay"
on the other machine.
>
> --
> Regards,
>
> Wiktor Wodecki
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2003-11-14 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 12:38 [linux-lvm] Cuncurrent access to a vg from two hosts Wiktor Wodecki
2003-11-14 8:13 ` Heinz J . 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=20031114151201.H28265@sistina.com \
--to=mauelshagen@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.