* [linux-lvm] Shared LUN without CLM
@ 2016-09-20 16:07 Руденко Александр
2016-09-21 11:46 ` Zdenek Kabelac
0 siblings, 1 reply; 3+ messages in thread
From: Руденко Александр @ 2016-09-20 16:07 UTC (permalink / raw)
To: linux-lvm
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.
Sorry for my english)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-lvm] Shared LUN without CLM
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
0 siblings, 1 reply; 3+ messages in thread
From: Zdenek Kabelac @ 2016-09-21 11:46 UTC (permalink / raw)
To: LVM general discussion and development
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..
Regards
Zdenek
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-lvm] Shared LUN without CLM
2016-09-21 11:46 ` Zdenek Kabelac
@ 2016-09-21 18:49 ` David Teigland
0 siblings, 0 replies; 3+ messages in thread
From: David Teigland @ 2016-09-21 18:49 UTC (permalink / raw)
To: fatruden; +Cc: linux-lvm
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-09-21 18:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).