From: David Teigland <teigland@redhat.com>
To: Eric Ren <zren@suse.com>, linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvmlockd: about the limitation on lvresizing the LV active on multiple nodes
Date: Wed, 3 Jan 2018 09:07:13 -0600 [thread overview]
Message-ID: <20180103150713.GA16217@redhat.com> (raw)
In-Reply-To: <be5b9aa6-d9fb-2e45-d250-9736d1ae49a5@suse.com>
On Wed, Jan 03, 2018 at 11:52:34AM +0800, Eric Ren wrote:
> > 1. one one node: lvextend --lockopt skip -L+1G VG/LV
> >
> > That option doesn't exist, but illustrates the point that some new
> > option could be used to skip the incompatible LV locking in lvmlockd.
>
> Hmm, is it safe to just skip the locking while the LV is active on other
> node?
> Is there somewhere in the code to avoid concurrent lvm command to execute
> at the same time?
The VG lock is still used to protect the VG metadata change. The LV lock
doesn't protect anything per se, it just represents that lvchange has
activated the LV on this host. (The LV lock does not represent the
suspended/resumed state of the dm device either, as you suggested above.)
I'll send a simple patch to skip the lv lock to try this.
Dave
next prev parent reply other threads:[~2018-01-03 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 10:42 [linux-lvm] lvmlockd: about the limitation on lvresizing the LV active on multiple nodes Eric Ren
2018-01-02 8:09 ` Eric Ren
2018-01-02 17:10 ` David Teigland
2018-01-03 3:52 ` Eric Ren
2018-01-03 15:07 ` David Teigland [this message]
2018-01-04 9:06 ` Eric Ren
2018-01-09 2:42 ` Eric Ren
2018-01-09 15:42 ` David Teigland
2018-01-10 6:55 ` Eric Ren
2018-01-10 15:56 ` David Teigland
2018-01-11 9:32 ` 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=20180103150713.GA16217@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).