* [linux-lvm] ubuntu xenial + lvmlockd
@ 2017-04-13 16:14 Charles Koprowski
2017-04-18 16:00 ` David Teigland
0 siblings, 1 reply; 4+ messages in thread
From: Charles Koprowski @ 2017-04-13 16:14 UTC (permalink / raw)
To: LVM general discussion and development
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
Hi all,
I'm trying to set up a shared VG between 2 ubuntu servers (xenial) using
lvmlockd for locking.
Unfortunately, even if the default config (lvm.conf) mentions the
possibillity to use lvmlockd (use_lvmlockd = 1), I cannot find any trace of
the daemon lvmlockd or lvmlockctl tool in ubuntu.
Does anyone already done this before ?
Do I have to build lvm from source in order to use lvmlockd ?
Thanks
Regards,
Charles
[-- Attachment #2: Type: text/html, Size: 660 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [linux-lvm] ubuntu xenial + lvmlockd
2017-04-13 16:14 [linux-lvm] ubuntu xenial + lvmlockd Charles Koprowski
@ 2017-04-18 16:00 ` David Teigland
2017-04-20 9:26 ` Charles Koprowski
0 siblings, 1 reply; 4+ messages in thread
From: David Teigland @ 2017-04-18 16:00 UTC (permalink / raw)
To: Charles Koprowski; +Cc: LVM general discussion and development
On Thu, Apr 13, 2017 at 06:14:54PM +0200, Charles Koprowski wrote:
> Hi all,
>
> I'm trying to set up a shared VG between 2 ubuntu servers (xenial) using
> lvmlockd for locking.
>
> Unfortunately, even if the default config (lvm.conf) mentions the
> possibillity to use lvmlockd (use_lvmlockd = 1), I cannot find any trace of
> the daemon lvmlockd or lvmlockctl tool in ubuntu.
>
> Does anyone already done this before ?
>
> Do I have to build lvm from source in order to use lvmlockd ?
I'd guess that lvm was not built with lvmlockd support, in which case you
would need to rebuild it with one or both of --enable-lockd-sanlock,
--enable-lockd-dlm (and I'm going to rename those options to be "lvmlockd"
in a minute.)
Dave
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [linux-lvm] ubuntu xenial + lvmlockd
2017-04-18 16:00 ` David Teigland
@ 2017-04-20 9:26 ` Charles Koprowski
2017-04-20 15:40 ` David Teigland
0 siblings, 1 reply; 4+ messages in thread
From: Charles Koprowski @ 2017-04-20 9:26 UTC (permalink / raw)
To: David Teigland; +Cc: LVM general discussion and development
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
2017-04-18 18:00 GMT+02:00 David Teigland <teigland@redhat.com>:
> On Thu, Apr 13, 2017 at 06:14:54PM +0200, Charles Koprowski wrote:
> > Hi all,
> >
> > I'm trying to set up a shared VG between 2 ubuntu servers (xenial) using
> > lvmlockd for locking.
> >
> > Unfortunately, even if the default config (lvm.conf) mentions the
> > possibillity to use lvmlockd (use_lvmlockd = 1), I cannot find any trace
> of
> > the daemon lvmlockd or lvmlockctl tool in ubuntu.
> >
> > Does anyone already done this before ?
> >
> > Do I have to build lvm from source in order to use lvmlockd ?
>
> I'd guess that lvm was not built with lvmlockd support, in which case you
> would need to rebuild it with one or both of --enable-lockd-sanlock,
> --enable-lockd-dlm (and I'm going to rename those options to be "lvmlockd"
> in a minute.)
>
Thank you David !
Would you consider the use of lvmlockd + sanlock as "production ready" ?
My goal here is to replace an existing cluster of 5 nodes using clvmd + dlm
+ corosync to access a shared VG of 6 TB containing around 300 LVs.
The current solution is working fine but I find using dlm + corosync "just"
for locking a bit overkill.
Regards,
Charles
[-- Attachment #2: Type: text/html, Size: 1831 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [linux-lvm] ubuntu xenial + lvmlockd
2017-04-20 9:26 ` Charles Koprowski
@ 2017-04-20 15:40 ` David Teigland
0 siblings, 0 replies; 4+ messages in thread
From: David Teigland @ 2017-04-20 15:40 UTC (permalink / raw)
To: Charles Koprowski; +Cc: LVM general discussion and development
On Thu, Apr 20, 2017 at 11:26:18AM +0200, Charles Koprowski wrote:
> Would you consider the use of lvmlockd + sanlock as "production ready" ?
I believe it will work better than clvmd. There is one main thing, unique
to using sanlock, that you should verify in your environment.
lvmlockd+sanlock is sensitive to spikes in i/o delays. If sanlock sees
several consecutive large i/o delays (> 10 sec each), e.g. during heavy
use from applications, or during path switching, this can trigger spurious
failure detection. (This is analogous to network delays when using
network-based solutions.)
(We can increase i/o timeouts to compensate if really necessary.)
> My goal here is to replace an existing cluster of 5 nodes using clvmd + dlm
> + corosync to access a shared VG of 6 TB containing around 300 LVs.
>
> The current solution is working fine but I find using dlm + corosync "just"
> for locking a bit overkill.
I agree.
Dave
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-04-20 15:40 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-04-13 16:14 [linux-lvm] ubuntu xenial + lvmlockd Charles Koprowski
2017-04-18 16:00 ` David Teigland
2017-04-20 9:26 ` Charles Koprowski
2017-04-20 15:40 ` David Teigland
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.