Re: Usynced blocks if replication is interrupted during initial sync

: Philipp Reisner Sent: Thursday, April 4, 2024 1:06 PM To: Tim Westbrook Cc: drbd-user@lists.linbit.com Subject: Re: Usynced blocks if replication is interrupted during initial sync   [Caution - External] Hello Tim, We were able to write a reproducer test case and fix this regression with this commit

Re: Usynced blocks if replication is interrupted during initial sync

? Thanks so much for your help Cheers, Tim From: Joel Colledge Sent: Wednesday, March 20, 2024 12:02 AM To: Tim Westbrook Cc: drbd-user@lists.linbit.com Subject: Re: Usynced blocks if replication is interrupted during initial sync   [Caution - External] > We are still seeing the is

Re: Usynced blocks if replication is interrupted during initial sync

Please ignore my Question, I just saw the response from Philipp From: Tim Westbrook Sent: Monday, April 15, 2024 7:09 PM To: Joel Colledge Cc: drbd-user@lists.linbit.com Subject: Re: Usynced blocks if replication is interrupted during initial sync Hi Joel I

Re: Usynced blocks if replication is interrupted during initial sync

Thank you! From: Philipp Reisner Sent: Thursday, April 4, 2024 1:06 PM To: Tim Westbrook Cc: drbd-user@lists.linbit.com Subject: Re: Usynced blocks if replication is interrupted during initial sync [Caution - External] Hello Tim, We were able to write

Re: Usynced blocks if replication is interrupted during initial sync

fails many blocks > > > > > From: Joel Colledge > Sent: Wednesday, March 20, 2024 12:02 AM > To: Tim Westbrook > Cc: drbd-user@lists.linbit.com > Subject: Re: Usynced blocks if replication is interrupted during initial sync > > [Caution - External] > &

Re: Usynced blocks if replication is interrupted during initial sync

0 message here 22. drbdadm verify persist - fails many blocks From: Joel Colledge Sent: Wednesday, March 20, 2024 12:02 AM To: Tim Westbrook Cc: drbd-user@lists.linbit.com Subject: Re: Usynced blocks if replication is interrupted during initial sync   [Caution - External] > We are

Re: Usynced blocks if replication is interrupted during initial sync

> 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

Re: Usynced blocks if replication is interrupted during initial sync

Colledge Sent: Tuesday, March 19, 2024 1:56 AM To: Tim Westbrook Cc: drbd-user@lists.linbit.com Subject: Re: Usynced blocks if replication is interrupted during initial sync   [Caution - External] Hi Tim, Thanks for the report and your previous one with the subject line "Blocks fail to syn

Re: Usynced blocks if replication is interrupted during initial sync

Hi Tim, Thanks for the report and your previous one with the subject line "Blocks fail to sync if connection lost during initial sync". This does look like a bug. I can reproduce the issue. It appears to be a regression introduced in drbd-9.1.16 / drbd-9.2.5. Specifically, with the following

Usynced blocks if replication is interrupted during initial sync

A follow up to my previous message, we are still seeing unsynced blocks on re-connect, and it happens with just a single secondary 1. Create config on primary with only 1 node (itself) as primary 2. Add another node by modifying the primary config file , and performing an adjust 3. Update the