Re: [linux-lvm] [lvmlockd] recovery lvmlockd after kill_vg

[David Teigland <teigland@redhat.com>]

On Thu, Sep 27, 2018 at 10:12:44PM +0800, Damon Wang wrote:
> Thank you for your reply, I have another question under such circumstances.
> 
> I usually run "vgck" to check weather vg is good, but sometimes it
> seems it stuck, and leave a VGLK on sanlock. (I'm sure io error will
> cause it, but sometimes not because io error)
> Then i'll try use sanlock client release -r xxx to release it, but it
> also sometimes not work.(be stuck)
> Then I may lvmlockctl -r to drop vg lockspace, but it still may stuck,
> and I'm io is ok when it stuck
> 
> This usually happens on multipath storage, I consider multipath will
> queue some io is blamed, but not sure.
> 
> Any idea?

First, you might be able to avoid this issue by doing the check using
something other than an lvm command, or perhaps and lvm command configured
to avoid taking locks (the --nolocking option in vgs/pvs/lvs).  What's
appropriate depends on specifically what you want to know from the check.

I still haven't fixed the issue you found earlier, which sounds like it
could be the same or related to what you're describing now.
https://www.redhat.com/archives/linux-lvm/2018-July/msg00011.html

As for manually cleaning up a stray lock using sanlock client, there may
be some limits on the situations that works in, I don't recall off hand.
You should try using the -p <pid> option with client release to match the
pid of lvmlockd.

Configuring multipath to fail more quickly instead of queueing might give
you a better chance of cleaning things up.

Dave