Linux block layer
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: Haris Iqbal <haris.iqbal@ionos.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-block@vger.kernel.org,
	Jia Li <jia.li@ionos.com>
Subject: Re: [LSF/MM/BPF TOPIC] A block level, active-active replication solution
Date: Tue, 5 May 2026 11:19:57 +0200	[thread overview]
Message-ID: <afm2PewS5Gi5QU61@ryzen9> (raw)
In-Reply-To: <CAJpMwyiVqqbR3ni+URv0uPnE0Bgt_+d+-_+_t6E3wzfiUOT-cg@mail.gmail.com>

Am Tue, Feb 03, 2026 at 04:09:59PM +0100 schrieb Haris Iqbal:
> Hi Haris,
> 
> We are working on a pair of kernel modules which would offer a new
> replication solution in the Linux kernel. It would be a block level,
> active-active replication solution for RDMA transport.
> 
> The existing block level replication solution in the Linux kernel is
> DRBD, which is an active-passive solution. The data replication in
> DRBD happens through 2 network hops.
>
>
> An active-active solution which one can build is by exporting block
> devices, either through NVMeOF or RNBD/RTRS, over the network, and
> then creating a raid1 device over it. It would provide a single hop
> replication solution, but the synchronization during a degraded state
> goes through 2 hops.
> 
> The proposed solution would provide an active-active single hop
> replication, and a single hop synchronization (directly between
> storage nodes) in case of a degraded state.
[...]


I stumbled across this post because of the newer replies.

I want to point out that we have significantly developed DRBD over the
last 15 Years as an out-of-tree module. In the past months, we began
the process of getting all those improvements back into Linux
upstream.

With that, DRBD9 became multi-node. It does the “active-active single
hop replication” as it is. The networking part is now abstracted into
transport modules. We have one for TCP, one for load balancing across
multiple TCP connections, and one for RDMA.

What you are doing here, in DRBD lingo, is a diskless primary
connected to multiple storage nodes.

Find everything here https://github.com/LINBIT.
The latest edition of what we bring to the upstreaming discussion:
https://github.com/LINBIT/linux-drbd/tree/drbd-next

Philipp

      parent reply	other threads:[~2026-05-05  9:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 15:09 [LSF/MM/BPF TOPIC] A block level, active-active replication solution Haris Iqbal
2026-02-03 18:01 ` Bart Van Assche
2026-02-03 18:04   ` Haris Iqbal
2026-02-10 13:06     ` Haris Iqbal
2026-02-10 18:31       ` Bart Van Assche
2026-02-13 14:13         ` Haris Iqbal
2026-02-13 17:32 ` Bart Van Assche
2026-02-19 10:43   ` Haris Iqbal
2026-04-29 14:26     ` Haris Iqbal
2026-05-01 19:47 ` [Lsf-pc] " Matthew Wilcox
2026-05-02 11:41   ` Keith Busch
2026-05-04  8:24     ` Haris Iqbal
2026-05-05  9:19 ` 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=afm2PewS5Gi5QU61@ryzen9 \
    --to=philipp.reisner@linbit.com \
    --cc=haris.iqbal@ionos.com \
    --cc=jia.li@ionos.com \
    --cc=linux-block@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    /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