Hi Joel I was never able to get the invalidate steps you outlined to work for our set up.
We downgraded to 9.2.4 kernel driver (the release prior to your referenced commit) and no longer see the issue. Do you know if this issue will be addressed in the next released version of the driver? Thanks so much for your help Cheers, Tim From: Joel Colledge <joel.colle...@linbit.com> Sent: Wednesday, March 20, 2024 12:02 AM To: Tim Westbrook <tim_westbr...@selinc.com> Cc: drbd-user@lists.linbit.com <drbd-user@lists.linbit.com> Subject: Re: Usynced blocks if replication is interrupted during initial sync [Caution - External] > We are still seeing the issue as described but perhaps I am not putting the > invalidate > at the right spot > > Note - I've added it at step 6 below, but I'm wondering if it should be after > the additional node is configured and adjusted (in which case I would need to > unmount as apparently you can't invalidate a disk in use) > > So do I need to invalidate after every node is added? With my reproducer, the workaround at step 6 works. > Also Note, the node-id in the logs from the kernel is 0 but peers are > configured with 1 and 2 , > is this an issue or they separate ids? I presume you are referring to the line: "Copying bitmap of peer node_id=0" The reason that node ID 0 appears here is that DRBD stores a bitmap of the blocks that have changed since it was first brought up. This is the "day0" bitmap. This is stored in all unused bitmap slots. All unused node IDs point to one of these bitmaps. In this case, node ID 0 is unused. So this line means that it is using the day0 bitmap here. This is unexpected, as mentioned in my previous reply. Joel
