From: David Teigland <teigland@redhat.com>
To: fatruden@yandex.com
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Shared LUN without CLM
Date: Wed, 21 Sep 2016 13:49:17 -0500 [thread overview]
Message-ID: <20160921184917.GB11843@redhat.com> (raw)
In-Reply-To: <7d6b51cd-1b39-4931-a4c6-6af80459c847@redhat.com>
On Wed, Sep 21, 2016 at 01:46:12PM +0200, Zdenek Kabelac wrote:
> Dne 20.9.2016 v 18:07 Руденко Александр napsal(a):
> >Hi, friends.
> >
> >I have strange question)
> >
> >I have one shared LUN on many different hosts.
> >LUN is PV in some VG.
> >
> >Each hosts can make any operation in this VG - create LV, remove LV, resize LV, etc.
> >If i want access to same LV on same host, i take "lvscan" and "lvchange -aey /dev/VG/LV_name".
> >I'm sure can't two modification VG in same time.
> >
> >It work fine for me.
> >
> >My question.
> >
> >Can i not use the CLVM extension?
> >
> >CLVM is great extension for LVM, but i will have more 100 nodes.
> >This count not supported in corosync.
>
>
> There is now (slowly) introduce another clustered locking support where
> the instead of 'dlm' locking engine it's using 'sanlock'
>
> It's targeting the 'many-nodes' clusters, might be likely worth to check.
>
> It has some advantages over clvmd/dlm and on the other hand some
> features are missing (i.e. remove node activation).
>
> But from the context you've show - it seems like it might be a good
> fit to start playing with..
See here for more information:
http://man7.org/linux/man-pages/man8/lvmlockd.8.html
prev parent reply other threads:[~2016-09-21 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 16:07 [linux-lvm] Shared LUN without CLM Руденко Александр
2016-09-21 11:46 ` Zdenek Kabelac
2016-09-21 18:49 ` David Teigland [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=20160921184917.GB11843@redhat.com \
--to=teigland@redhat.com \
--cc=fatruden@yandex.com \
--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).