[linux-lvm] [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..."

David Teigland teigland at redhat.com
Fri Oct 12 14:21:07 UTC 2018

On Fri, Oct 12, 2018 at 04:58:45PM +0800, Damon Wang wrote:
> 1. Is this bug easy to repeat (seems need lease owner committed by a
> host is not the lease leader)?

It will happen occasionally, depending entirely on timing, when there are
commands running concurrently on different hosts that need the same lock.

> 2. I find the commit 6501351b742 introduced bug is released with
> 3.6.0, if I want to fix it, which is recommend, make a master build or
> downgrade to 3.5.0?

I suggest applying the patch onto 3.6.0.


More information about the linux-lvm mailing list