mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ameer Hamza <ameer.hamza@truenas.com>
To: Alexander Aring <aahringo@redhat.com>
Cc: David Teigland <teigland@redhat.com>,
	gfs2@lists.linux.dev,  linux-kernel@vger.kernel.org,
	caleb.stjohn@truenas.com
Subject: Re: [PATCH] dlm: don't set RSB_MASTER_UNCERTAIN on rsb with no master
Date: Tue, 3 Nov 2026 02:03:13 +0500	[thread overview]
Message-ID: <auj4LE0bq7w7lOF8@hamza-PC> (raw)
In-Reply-To: <CAK-6q+jBNKN=oSCmm+i011FdhPS+42BZc0iUfbqGiLDBc0Py5A@mail.gmail.com>

On Mon, Nov 02, 2026 at 03:38:12PM -0500, Alexander Aring wrote:
> Hi,
> 
> On Mon, Nov 2, 2026 at 3:03 PM Ameer Hamza <ameer.hamza@truenas.com> wrote:
> >
> > On Mon, Nov 02, 2026 at 02:49:04PM -0500, Alexander Aring wrote:
> > > question:
> > >
> > > how do you "pause" anything in DLM?
> >
> > The nodes are VMs, so I freeze the dir node from the QEMU monitor. It
> > stays a member but never answers the lookup, and after the cancel I
> > evict it through configfs. That is what happens on our HA systems when
> > the peer reboots without leaving the lockspace and a pending request
> > gets cancelled before the peer is evicted.
> 
> Still, do you just randomly freeze it, or do you busy/poll wait on
> specific struct field changes?

I don't poll anything. The peer is frozen before the request is made,
so the lookup to it can never complete. Then the request is cancelled,
the peer is evicted and the name is requested again, and it asserts
every time.

Best Regards,
Ameer Hamza

  reply	other threads:[~2026-11-02 21:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 15:16 Ameer Hamza
2026-11-02 13:11 ` Ameer Hamza
2026-11-02 19:49 ` Alexander Aring
2026-11-02 20:03   ` Ameer Hamza
2026-11-02 20:38     ` Alexander Aring
2026-11-02 21:03       ` Ameer Hamza [this message]
2026-11-02 22:22         ` Alexander Aring

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=auj4LE0bq7w7lOF8@hamza-PC \
    --to=ameer.hamza@truenas.com \
    --cc=aahringo@redhat.com \
    --cc=caleb.stjohn@truenas.com \
    --cc=gfs2@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=teigland@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

all inboxes | Powered by JetHome®