From: Philipp Reisner <philipp.reisner@linbit.com>
To: Amirhossein Rahimi <amh.rhimi@gmail.com>
Cc: drbd-dev@lists.linux.dev
Subject: Re: [BUG] DRBD 9.3.4: acknowledgement counter rewind and stalled resync after failover
Date: Mon, 28 Sep 2026 18:03:49 +0200 [thread overview]
Message-ID: <arqP5STzDsErl0KN@fw13-phil> (raw)
In-Reply-To: <CAFQ+Lwv41X=4BFLeWEdacOHowB5M6KojJ8fG90-U+sCNhLkWZg@mail.gmail.com>
Hello,
thank you for the careful report.
I can confirm the problem is real. We reproduced it in our lab and it now has
an automated regression test. Your diagnosis points at the right place: a write
that never gets a dagtag assigned can move the peer-acknowledgement tracking
backwards, after which the resync waits for a flush acknowledgement that is
never sent. That also explains why the data compared equal — nothing was
actually out of sync.
A fix is in review. We expect to have it available within the next few days,
and I will come back to you once it is merged.
Best regards,
Philipp
prev parent reply other threads:[~2026-09-28 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 6:22 [BUG] DRBD 9.3.4: acknowledgement counter rewind and stalled resync after failover Amirhossein Rahimi
2026-09-28 16:03 ` Philipp Reisner [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=arqP5STzDsErl0KN@fw13-phil \
--to=philipp.reisner@linbit.com \
--cc=amh.rhimi@gmail.com \
--cc=drbd-dev@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.