From: Damon Wang <firstname.lastname@example.org>
To: David Teigland <email@example.com>
Cc: LVM general discussion and development <firstname.lastname@example.org>
Subject: Re: [linux-lvm] [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..."
Date: Fri, 12 Oct 2018 16:58:45 +0800 [thread overview]
Message-ID: <CABZYMH4+6HiCPGROZoBHhraB0wfX5UQYJNZRZ4RjROfLDkZMxQ@mail.gmail.com> (raw)
Thanks for your mail, I read the patch and have some questions:
1. Is this bug easy to repeat (seems need lease owner committed by a
host is not the lease leader)?
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?
On Fri, Oct 12, 2018 at 2:58 AM David Teigland <email@example.com> wrote:
> > > 2018-10-09 20:49:16 4854717 : r2320 write_host_block host_id
> > > 19 flags 1 gen 1 dblock 29802:510:140245418403952:140245440585933:140245418403840:4:RELEASED.
> > Perfect, that shows exactly where the bug is. There's a case where it has
> > missed saving the latest dblock values, so random values are being copied
> > back to the dblock instead. I'll push out a patch once I've had a chance
> > to test it.
> Here's the fix:
> Thanks for the help finding that.
next prev parent reply other threads:[~2018-10-12 8:58 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 [this message]
2018-10-12 14:21 ` David Teigland
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).