From: David Teigland <teigland@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH LVM2 v1 2/2] lvmlockctl: Automatically handle failure
Date: Mon, 1 Mar 2021 18:40:51 -0600 [thread overview]
Message-ID: <20210302004051.GA20678@redhat.com> (raw)
In-Reply-To: <20210225110451.175956-2-leo.yan@linaro.org>
On Thu, Feb 25, 2021 at 07:04:51PM +0800, Leo Yan wrote:
> From: Zhang Huan <zhanghuan@huayun.com>
>
> When the lock manager detects drive failure, it invokes command
> "lvmlockctl" to handle the faiulre; in this case, lvmlockctl
> automatically calls "blkdeactivate -l forcevg" to deactivate VG
> and calls drop_vg() to cleanup the lockspace.
Hi, I have a couple commits to replace this one, which make it
configurable. There are a couple small things left to look at.
See this branch:
https://sourceware.org/git/?p=lvm2.git;a=shortlog;h=refs/heads/dev-dct-lvmlockctl-kill-1
I've been testing this by just setting lvm.conf
lvmlockctl_kill_command="vgchange -an"
and running lvmlockctl --kill <vgname>
We'll likely leave lvmlockctl_kill_command empty (disabled) by default for
now, with a suggestion to consider the blkdeactivate command.
Dave
next prev parent reply other threads:[~2021-03-02 0:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 11:04 [PATCH LVM2 v1 1/2] blkdeactive: Introduce option "forcevg" to forcibly deactivate VG Leo Yan
2021-02-25 11:04 ` [PATCH LVM2 v1 2/2] lvmlockctl: Automatically handle failure Leo Yan
2021-03-02 0:40 ` David Teigland [this message]
2021-03-02 17:52 ` David Teigland
2021-03-03 3:48 ` Leo Yan
2021-02-25 12:01 ` [PATCH LVM2 v1 1/2] blkdeactive: Introduce option "forcevg" to forcibly deactivate VG Zdenek Kabelac
2021-02-25 12:39 ` Leo Yan
2021-02-25 12:54 ` Zdenek Kabelac
2021-02-25 16:47 ` 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=20210302004051.GA20678@redhat.com \
--to=teigland@redhat.com \
--cc=lvm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.