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] lvmlockd: how to convert lock_type from sanlock to dlm?
Date: Mon, 20 Nov 2017 10:10:07 -0600	[thread overview]
Message-ID: <20171120161007.GA29888@redhat.com> (raw)
In-Reply-To: <dc362b54-42cf-025d-ec3a-22e14abc4745@suse.com>

On Mon, Nov 20, 2017 at 06:35:20PM +0800, Eric Ren wrote:
> On my testing cluster,� the lvmlockd was firstly used with sanlock and
> everything was OK.  After some play, I want to change the "sanlock"
> lock_type of a VG into "dlm" locktype.

> # vgchange --lock-type none --force vg1������ // the cmd comes from `man lvmlockd`
> Command does not accept option: --force.

First you'll need this recent fix:
https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=f611b68f3c02b9af2521d7ea61061af3709fe87c

--force was broken at some point, and the option is now --lockopt force.

To change between lock types, you are supposed to be able to change to a
local VG, then from local to the other lock type.  The man page sections:

  changing a lockd VG to a local VG
  changing a local VG to a lockd VG

But it looks like a fix is needed in those instructions.  I believe
"vgchange --lock-type none <vgname>" needs to include --lockopt force.
If you could verify this for me, I'll update the man page.
Thanks
Dave

  reply	other threads:[~2017-11-20 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 10:35 [linux-lvm] lvmlockd: how to convert lock_type from sanlock to dlm? Eric Ren
2017-11-20 16:10 ` David Teigland [this message]
2017-11-21  4:11   ` Eric Ren

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=20171120161007.GA29888@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).