archive mirror
 help / color / mirror / Atom feed
From: David Teigland <>
Cc: Eric Ren <>
Subject: Re: [linux-lvm] The benefits of lvmlockd over clvmd?
Date: Wed, 10 Jan 2018 11:25:29 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Jan 10, 2018 at 04:35:56PM +0100, Zdenek Kabelac wrote:
> > > Also ATM� 'lvmetad' can't be used even with lvmlockd - simply
> > > because we are not (yet) capable to handle 'udev' around the cluster
> > > (and it's not clear we ever will).
> > 
> > This sentence surprises me much. According to manpage of lvmlockd, it

It surprises me too, since I developed lvmlockd and lvmetad features
precisely to make it work.

> > seems clear that lvmlockd can work with lvmetad now.
> > IIRC, it's not the first time you mentioned about "cluster udev". It
> > gives me a impression that the currect udev system is not
> > 100% reliable for shared disks in cluster, no matter if we use lvmetad
> > or not, right? If so, could you please give an example
> > scenario where lvmetad may not work well with lvmlockd?
> The world of udevd/systemd is complicated monster - which has no notation for
> handling bad/duplicate/.... devices and so on.
> Current design of lvmetad is not sufficient to live in ocean of bugs in this
> category - so as said - ATM it's highly recommend to keep lvmetad off in
> clusters.

There are indeed plenty of problems with lvmetad, which is why I've been
trying to get us to get rid of lvmetad, and improved disk scanning to be
so much more efficient:;a=shortlog;h=refs/heads/dev-dct-new-scan-32

However, you have not pointed out any specific problems unique to lvmlockd
with lvmetad.

  reply	other threads:[~2018-01-10 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09  3:15 [linux-lvm] The benefits of lvmlockd over clvmd? Eric Ren
2018-01-09 16:06 ` David Teigland
2018-01-10  7:11   ` Eric Ren
2018-01-10  9:36     ` Zdenek Kabelac
2018-01-10 14:42       ` Eric Ren
2018-01-10 15:35         ` Zdenek Kabelac
2018-01-10 17:25           ` David Teigland [this message]
2018-01-10 16:45     ` David Teigland

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).