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 UpTpDa
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 F
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
___
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
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 "OutD
Hi all,
On drbd-9.0.23 (CentOS 8.2), we are facing an inconsistence of node status.
That is, although the state of both DRBD device is UpToDate, there exists
some out-of-sync value.
#drbdsetup status --verbose --statistics
r008 node-id:0 role:Primary suspended:no
write-ordering:flush
volume:0
