linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Damon Wang <damon.devops@gmail.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] [lvmlockd] lvm command hung with sanlock log "ballot 3 abort1 larger lver in bk..."
Date: Thu, 11 Oct 2018 10:55:04 -0500	[thread overview]
Message-ID: <20181011155504.GA17418@redhat.com> (raw)
In-Reply-To: <CABZYMH7MCecO37Fav-6GH=vWzcR56XG3T0Gx4heRWR8k1QtcOQ@mail.gmail.com>

On Thu, Oct 11, 2018 at 09:03:01PM +0800, Damon Wang wrote:
> This is because I regenerate a host id when the host join a new
> lockspace

OK, I guess there's something about your setup that makes it difficult to
assign static host_id's.

>  2018-10-09 20:49:16 4854717 [29802]: 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.

> does the "paxos_release skip write last lver" is abnormal?

Not very unusual when you have lock contention (multiple hosts trying to
acquire the same lock concurrently.)

Thanks,
Dave

  reply	other threads:[~2018-10-11 15:55 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 [this message]
2018-10-11 18:58       ` David Teigland
2018-10-12  8:58         ` Damon Wang
2018-10-12 14:21           ` David Teigland

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=20181011155504.GA17418@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).