linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Eric Ren <zren@suse.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] New features for using lvm on shared storage
Date: Tue, 10 Jan 2017 09:30:59 -0600	[thread overview]
Message-ID: <20170110153059.GA26789@redhat.com> (raw)
In-Reply-To: <4d90b417-b9cc-12a0-67ef-5b5886d9c456@suse.com>

On Tue, Jan 10, 2017 at 09:02:36PM +0800, Eric Ren wrote:
> Hi David,
> 
> Sorry for faking this reply because I'm not in the maillist before I noticed
> this email (quoted blow) you posted for a while.
> 
> I have a questions about "lvmlockd":
> 
> Besides clvmd cannot be used together with lvmetad, is there any other
> main differences between "lvmetad" and "clvmd"? Do you recommend we replace
> "clvmd" with "lvmetad"?

Hi, I think you're looking at the differences between lvmlockd and clvmd.
They have a completely different design and implementation, with lvmlockd
being much simpler and more obvious in what it does and how it works.
clvm was sort of designed around the old concept of a "single system
image" across a cluster, and tried hard to hide any difference between
local/shared VGs.  lvmlockd just inserts lock/unlock around disk
modifications when the VG is shared.  And as mentioned before, lvmlockd
can use sanlock which opens it up to new uses where a cluster doesn't fit.
I recommend replacing clvm with lvmlockd; I think it works better, and
clvm will eventually be phased out.

(lvmetad, the metadata caching daemon, can indeed be used with lvmlockd,
and not clvmd, but this is not a big advantage.  The metadata caching has
not turned out to be much of a benefit.)

> """
> 
> For people using LVM (or clvm) on shared storage, I encourage you to take
> a look at two recent additions that you may find to be an improvement:
> 
> 1. System ID
> 
> is for static ownership of VGs by hosts:
> http://man7.org/linux/man-pages/man7/lvmsystemid.7.html
> 
> The nearest equivalent to system ID in the past has been configuring
> lvm.conf filters uniquely on each host.
> 
> 2. lvmlockd
> 
> is for dynamically sharing VGs among hosts:
> http://man7.org/linux/man-pages/man8/lvmlockd.8.html
> 
> Using lvmlockd with dlm is similar to what clvmd has done in the past.
> Using lvmlockd with sanlock has no prior equivalent.
> 
> (For distribution packaging, see the "lvm2-lockd" rpm.)
> 
> Dave
> """

  reply	other threads:[~2017-01-10 15:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 13:02 [linux-lvm] New features for using lvm on shared storage Eric Ren
2017-01-10 15:30 ` David Teigland [this message]
2017-01-11  2:03   ` Eric Ren
  -- strict thread matches above, loose matches on Subject: below --
2016-11-22 16:23 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:
  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=20170110153059.GA26789@redhat.com \
    --to=teigland@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=zren@suse.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).