Hi, all We received the following responses from community developers. - States such as "UpToDate" are calculated based on the UUID comparison results. - "out-of-sync" is calculated according to the bitmap settings. - Because the calculation method is different between the two Even in the UpTpDate state, it occurs when out-oy-sync is not 0.
However, the following two points are doubtful. 1.This does not occur with DRBD 8.x Is this a specification designed after DRBD 9.x? Or is it the same specification as DRBD 8.x? 2.If you execute verify in this case, you can see that there are unsynchronized blocks. When this phenomenon occurs, if you execute the "drbdadm verify" command, You can see that asynchronous blocks remain. However, it seems strange that the disk status is UpToDate. Can anyone give us an opinion on the above two points? Regards Shuhei On Thu, Mar 31, 2022 at 9:46 AM Shuhei Tsutsumi <stsuts...@mvista.com> wrote: > Hi all, > > There are facts found in additional investigations. > > Even in the same UpToDate state > This issue occurs if the transition source is Outdated. > However, if the transition source is Inconsistent, this problem does not > occur at all. > > What is the difference between the two? > > Regards > Shuhei > > On Fri, Mar 25, 2022 at 8:47 PM Harald Dunkel <harald.dun...@aixigo.com> > wrote: > >> >> Hi folks, >> >> I would be highly interested in a explanation (and a possible workaround >> or fix?) for this inconsistency, too. How comes that drbd doesn't ring all >> alarm bells it has access to in such a situation? Is this considered as >> "not important"? >> >> >> Regards >> >> Harri >> _______________________________________________ >> Star us on GITHUB: https://github.com/LINBIT >> drbd-user mailing list >> drbd-user@lists.linbit.com >> https://lists.linbit.com/mailman/listinfo/drbd-user >> >
_______________________________________________ Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list drbd-user@lists.linbit.com https://lists.linbit.com/mailman/listinfo/drbd-user