From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Kalyana sundaram <kalyanceg@gmail.com>
Subject: Re: [linux-lvm] Distributed Locking of LVM
Date: Tue, 29 Aug 2017 11:25:19 +0200 [thread overview]
Message-ID: <ebead878-135f-a69c-455a-0c08e4947996@redhat.com> (raw)
In-Reply-To: <CABWX_dqg3za8oGq9-ohoCvDiJbmLs36Jgqy2a6NSa82Gxrr8tg@mail.gmail.com>
Dne 28.8.2017 v 14:41 Kalyana sundaram napsal(a):
> We have a shared iscsi disk at all our boxes, with one vg. We are using clvm
> to manage locks to create extend activate delete list.
> CLVM is tedious to manage especially especially due to reboot if locking is
> struck somewhere. Instead we are thinking of modifying file_locking.c to get
> lock with distributed store like zookeeper or redis and on success run the
> above command, on failure backoff and try again
> The external ocking code will sit at _file_lock_resource, case LCK_VG.
> Do you think its risky. Is there some other way people handle it?
>
Hi
Have you considered usage of 'lvmlockd' and it's sanlock interface
(where locks are maintained on shared storage device).
Regards
Zdenek
next prev parent reply other threads:[~2017-08-29 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 12:41 [linux-lvm] Distributed Locking of LVM Kalyana sundaram
2017-08-29 7:05 ` Digimer
2017-08-29 9:25 ` Zdenek Kabelac [this message]
2017-08-29 16:23 ` David Teigland
2017-08-31 6:32 ` Kalyana sundaram
2017-08-31 8:08 ` Zdenek Kabelac
2017-08-31 19:29 ` John Stoffel
2017-09-01 7:37 ` Peter Rajnoha
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=ebead878-135f-a69c-455a-0c08e4947996@redhat.com \
--to=zkabelac@redhat.com \
--cc=kalyanceg@gmail.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).