From: Tomasz Chmielewski <mangoo@wpkg.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] is LVM cluster-aware?
Date: Thu, 24 Jan 2008 18:20:25 +0100 [thread overview]
Message-ID: <4798C8D9.6020506@wpkg.org> (raw)
Is LVM cluster-aware? Of course it's not, but... Will I loose data if I
have a LVM physical volume replicated on two machines with DRBD, and I
want to access two separate logical volumes on different machines?
Machine_1
\ /--Logical_volume_1
DRBD-LVM2-PV
/ \--Logical_volume_2
Machine_2
On Machine_1 I only want to read/write to Logical_volume_1.
On Machine_2 I only want to read/write to Logical_volume_2.
I don't want to add/remove/rename/resize/etc. any volumes - just access
them on separate machines.
Perhaps the answer is: yes, you will loose your data, but I wanted to be
sure ;)
Are there any workarounds to that (with just two volumes it's simple -
don't use LVM; but let's suppose there are many logical volumes)?
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2008-01-24 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 17:20 Tomasz Chmielewski [this message]
2008-01-24 17:29 ` [linux-lvm] is LVM cluster-aware? Bryn M. Reeves
2008-01-25 15:33 ` Tomasz Chmielewski
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=4798C8D9.6020506@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).