From: David Teigland <teigland@redhat.com>
To: Damon Wang <damon.devops@gmail.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..."
Date: Fri, 12 Oct 2018 09:21:07 -0500 [thread overview]
Message-ID: <20181012142107.GA22320@redhat.com> (raw)
In-Reply-To: <CABZYMH4+6HiCPGROZoBHhraB0wfX5UQYJNZRZ4RjROfLDkZMxQ@mail.gmail.com>
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.
Dave
prev parent reply other threads:[~2018-10-12 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 7:51 [linux-lvm] [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..." Damon Wang
2018-10-10 7:58 ` Damon Wang
2018-10-10 8:12 ` Damon Wang
2018-10-10 19:08 ` David Teigland
2018-10-11 13:03 ` Damon Wang
2018-10-11 15:55 ` David Teigland
2018-10-11 18:58 ` David Teigland
2018-10-12 8:58 ` Damon Wang
2018-10-12 14:21 ` David Teigland [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=20181012142107.GA22320@redhat.com \
--to=teigland@redhat.com \
--cc=damon.devops@gmail.com \
--cc=linux-lvm@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).