From: Digimer <lists@alteeve.ca>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm2 cluster aware
Date: Thu, 25 Aug 2016 03:37:08 -0400 [thread overview]
Message-ID: <a0c7bedf-23d1-26c5-3853-0bd36f528185@alteeve.ca> (raw)
In-Reply-To: <CAN2gjWSEzL+M45UGFEkEA_i5bgNpKLXTQ+DAMPJjJJvBBvaTKQ@mail.gmail.com>
On 24/08/16 09:50 PM, su liu wrote:
> I have a question about lvm2 cluster, The scene is that I try to imitate
> FCSAN by mapping a rbd volume to two compute node, Then I using the rbd
> volume to create a PV and VG.I stoped the lvmetad daemon on the compute
> nodes. Then I find that when I operating the VG on one compute node, the
> changes can also be aware on another compute nodes.
>
> But this docment(http://www.tldp.org/HOWTO/LVM-HOWTO
> /sharinglvm1.html） says that "*LVM is not cluster aware".*
>
> My question is that can I use the method to achieve the case that I
> create or delete lv on one node whlie other compute node can using the lvs?
>
> Can anybody explain this?
>
> thx very much!
You can use DLM (distributed lock manager) to provide cluster locking to
LVM (locking_type = 3 via clvmd). This requires a cluster though, which
you can get with corosync + pacemaker (and use stonith!).
Further details/advice requires more understanding of your environment
and use-case. Feel free to pop over to Clusterlabs[1], as many of us do
this setup regularly. I use clustered LVM in all our HA setups and have
done so successfully for years.
digimer
1. http://clusterlabs.org/mailman/listinfo/users - freenode #clusterlabs
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
next prev parent reply other threads:[~2016-08-25 7:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 1:50 [linux-lvm] lvm2 cluster aware su liu
2016-08-25 7:37 ` Digimer [this message]
2016-08-25 15:59 ` David Teigland
2016-08-26 5:04 ` Digimer
2016-08-26 14:56 ` David Teigland
2016-08-25 8:49 su liu
2016-08-26 5:08 ` Digimer
2016-08-26 9:39 ` Lentes, Bernd
2016-08-26 6:28 su liu
2016-08-26 15:53 ` David Teigland
2016-08-26 6:35 su liu
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=a0c7bedf-23d1-26c5-3853-0bd36f528185@alteeve.ca \
--to=lists@alteeve.ca \
--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 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.