From: Damon Wang <damon.devops@gmail.com>
To: David Teigland <teigland@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] [lvmlockd] recovery lvmlockd after kill_vg
Date: Sat, 29 Sep 2018 02:13:38 +0800 [thread overview]
Message-ID: <CABZYMH5YLij+xwZQeC6K5KDAJtpL7hvv=3yXsQwVzsyRadgcqg@mail.gmail.com> (raw)
In-Reply-To: <20180928143203.GA5724@redhat.com>
It's really help, I noticed "sanlock client renewal" returns practical
information, but not noticed "sanlock client status -D", the later is
what I exactly want, thanks!
Damon
On Fri, Sep 28, 2018 at 10:32 PM David Teigland <teigland@redhat.com> wrote:
>
> On Fri, Sep 28, 2018 at 11:14:35AM +0800, Damon Wang wrote:
>
> > as the manual says, it should deactivate volumes and drop lockspace as
> > quick as possible,
>
> A year ago we discussed a more automated solution for forcing a VG offline
> when its sanlock lockspace was shut down:
>
> https://www.redhat.com/archives/lvm-devel/2017-September/msg00011.html
>
> The idea was to forcibly shut down LVs (using dmsetup wipe_table) in the
> VG when the kill_vg happened, then to automatically do the 'lvmlockctl
> --drop' when the LVs were safely shut down. There were some loose ends
> around integrating this solution that I never sorted out, so it's remained
> on my todo list.
>
> > TTY can get a message, but it's not a good way to listen or monitor, so I
> > run vgck periodically and parse its stdout and stderr, once "sanlock lease
> > storage failure" or
> > something unusual happens, an alert will be triggered and I'll do some
> > check(I hope all this process can be automatically).
>
> If you are specifically interested in detecting this lease timeout
> condition, there are some sanlock commands that can give you this info.
> You can also detect ahead of time that a VG's lockspace is getting close
> the threshold. I can get back to you with more specific fields to look
> at, but for now take a look at 'sanlock client renewal' and some of the
> internal details that are printed by 'sanlock client status -D'.
>
> Dave
prev parent reply other threads:[~2018-09-28 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 10:18 [linux-lvm] [lvmlockd] recovery lvmlockd after kill_vg Damon Wang
2018-09-25 16:44 ` David Teigland
2018-09-27 14:12 ` Damon Wang
2018-09-27 17:35 ` David Teigland
2018-09-28 3:14 ` Damon Wang
2018-09-28 14:32 ` David Teigland
2018-09-28 18:13 ` Damon Wang [this message]
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='CABZYMH5YLij+xwZQeC6K5KDAJtpL7hvv=3yXsQwVzsyRadgcqg@mail.gmail.com' \
--to=damon.devops@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=teigland@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 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).