From: Indivar Nair <indivar.nair@techterra.in>
To: Eric Ren <zren@suse.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Shared VG, Separate LVs
Date: Fri, 13 Oct 2017 16:10:53 +0530 [thread overview]
Message-ID: <CALuPYL3nMUm6of__zqAsadKoHkPpBYprH_QEpYmYv20vLhM18g@mail.gmail.com> (raw)
In-Reply-To: <611a15f8-dd20-ac38-8be4-afd050a82293@suse.com>
[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]
Thanks Eric,
I want to keep a single VG so that I can get the bandwidth (LVM Striping)
of all the disks (PVs)
PLUS
the flexibility to adjust the space allocation between both LVs. Each LV
will be used by different departments. With 1 LV on different hosts, I can
distribute the Network Bandwidth too.
I would also like to take snapshots of each LV before backing up.
I have been reading more about CLVM+Pacemaker options.
I can see that it is possible to have the same VG activated on multiple
hosts for a GFSv2 filesystem.
In which case, it is the same PVs, VG and LV getting activated on all hosts.
In my case, we will have the same PVs and VG activated on both hosts, but
LV1 on Host01 and LV2 on Host02. I paln to use ext4 or XFS filesystems.
Is there some possibility that it would work?
Regards,
Indivar Nair
On Fri, Oct 13, 2017 at 2:41 PM, Eric Ren <zren@suse.com> wrote:
> Hi,
>
> With CLVM / HA-LVM on a 2 node cluster -
>>
>> Is it possible to have a shared VG but separate LVs, with each LV
>> exclusively activated on different nodes in a 2 node cluster.
>> In case of a failure, the LV of the failed node will be activated on the
>> other node.
>>
>
> I think clvm can do what you want if you perform LVM commands by hand.
> But, with HA cluster manager (pacemaker) you cannot
> do it with the current resource agents (clvm + LVM) [1] [2], because they
> do failover at a VG basis.
>
> We are currently working on new resource agents [3] for lvmlockd [4]. The
> new agents can do activation on LV basis, but I won't
> recommend doing that if there's no strong reason. It makes things much
> more complicated.
>
> [1] https://github.com/ClusterLabs/resource-agents/blob/master/
> heartbeat/clvm
> [2] https://github.com/ClusterLabs/resource-agents/blob/master/
> heartbeat/LVM
> [3] https://www.redhat.com/archives/linux-lvm/2017-January/msg00025.html
> [4] https://github.com/ClusterLabs/resource-agents/pull/1040
>
> Eric
>
>
>
[-- Attachment #2: Type: text/html, Size: 3239 bytes --]
next prev parent reply other threads:[~2017-10-13 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALuPYL3fiHTGbxBFCeQw+HMEAwZBKs2HBMBuThnDFAHDCsDAsQ@mail.gmail.com>
[not found] ` <CALuPYL3NMm7xrfemcbQ7Kt511rL=VrS7cKi0J0HBKjq8z7QDyg@mail.gmail.com>
[not found] ` <CALuPYL2R1vLb5TY6CHEcC_m653oSyRHF2UBOU3if5fg2R8bCPg@mail.gmail.com>
[not found] ` <CALuPYL0ohSNtaC4N97WWUHbW3J8DfnzhT1Pd=iTe_pFvhN2tjw@mail.gmail.com>
[not found] ` <CALuPYL3EY2EjGER-Fhz0QW8Mu+LBE-L8oOAYo8=Eu9WwawCbgg@mail.gmail.com>
[not found] ` <CALuPYL1KRtc5e-ZQOqCKE4fyNt9WAgKzBNDdn-6N52yEEQxvEA@mail.gmail.com>
[not found] ` <CALuPYL26eMycV=h5ZLHTejWNSh-kwYdMKrNnfR7EfKNM83VBLQ@mail.gmail.com>
[not found] ` <CALuPYL1uwtmaCS8PoVd6F4Y9u4qqhqtyST0yZi77H7fNdi2XUQ@mail.gmail.com>
[not found] ` <CALuPYL1=MUfFawNOdSpSO-9az3m1vvWF3Y3jCrertFr5M3NewA@mail.gmail.com>
[not found] ` <CALuPYL2=kUoNv=VhvKqzqEM9E0QOe5vjeopGAC4oZ8_=0TUhDg@mail.gmail.com>
[not found] ` <CALuPYL2sLeTe8M7KgBGPbMkZWBQAGaOkkj0SS6ovHTg_0SCmuQ@mail.gmail.com>
2017-10-07 4:28 ` [linux-lvm] Shared VG, Separate LVs Indivar Nair
2017-10-13 9:11 ` Eric Ren
2017-10-13 10:40 ` Indivar Nair [this message]
2017-10-16 3:06 ` Eric Ren
2017-11-03 6:38 ` Indivar Nair
2017-11-14 4:52 ` Eric Ren
2017-11-22 5:49 ` Indivar Nair
2017-11-23 13:46 ` Eric Ren
2017-11-23 16:14 ` Indivar Nair
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=CALuPYL3nMUm6of__zqAsadKoHkPpBYprH_QEpYmYv20vLhM18g@mail.gmail.com \
--to=indivar.nair@techterra.in \
--cc=linux-lvm@redhat.com \
--cc=zren@suse.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).