Re: UpToDate and out-of-sync inconsistence
Shuhei Tsutsumi <[email protected]>
| Newsgroups | gmane.comp.linux.drbd |
|---|---|
| Message-ID | <CALDGcJqUU9r_ZqPumUxNzdvC4j-CAxd25SQoaPhaKDHZLn2ubg@mail.gmail.com> |
Hi all, I have confirmed that this problem can be reproduced with the latest drbd-9.1.16. On primary and secondary DRBD devices Both states are UpToDate, but there are values that are out of sync. Any feedback would be greatly appreciated. Best regards, shuhei On Fri, Mar 18, 2022 at 10:01 AM Shuhei Tsutsumi <[email protected]> wrote: > Hi all, > > I am continuing to investigate this. > As a result, I found one fact. > > This problem only occurs when the state transitions from "OutDated" to > "UpToDate". > And it never occurs when the state transitions from "Inconsistent" to > "UpTodate". > > Probably,I presume that the state transition from "OutDated" to "UpToDate" > is not exclusive in the state transition and asynchronous calculation. > > Is this a specification? Or is it a bug? > If it's a bug, where in the source code should I add exclusive processing? > > I'm worried because I don't know how to fix it. > I would be grateful if anyone could tell me. > > Best regards, > shuhei > > _______________________________________________ Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list [email protected] https://lists.linbit.com/mailman/listinfo/drbd-user