inSync bug ?

[frenzymind]

I have a clear installation of proxmox 6. Updated.
I install controller, satellite and client from proxmox-6 linbit repo:
"deb http://packages.linbit.com/proxmox/ proxmox-6 drbd-9.0"

Then I create resource:
LINSTOR ==> rd c test_rd
LINSTOR ==> vd c test_rd 1G
LINSTOR ==> r c vega test_rd -s drbd-sp

When I go to drbdtop, select this resource and press i:

I always see this number for any resource.
Container with this disk seems work normal.

[deleteriousEffect]

Could you provide the output of drbdsetup events2 --timestamps --statistics --now on that machine?

This seems like a repeat of a bug that was closed in #7 which was caused by downstream components.

[frenzymind]

Yes, here is output:

root@vega:~# drbdsetup events2 --timestamps --statistics --now
2019-08-18T02:29:24.637733+08:00 exists resource name:test_rd role:Secondary suspended:no write-ordering:flush 
2019-08-18T02:29:24.637733+08:00 exists device name:test_rd volume:0 minor:1001 disk:UpToDate client:no quorum:yes size:1052408 read:2901248 written:0 al-writes:0 bm-writes:0 upper-pending:0 lower-pending:0 al-suspended:no blocked:no
2019-08-18T02:29:24.637837+08:00 exists resource name:vm-100-disk-0 role:Secondary suspended:no write-ordering:flush
2019-08-18T02:29:24.637837+08:00 exists device name:vm-100-disk-0 volume:0 minor:1000 disk:UpToDate client:no quorum:yes size:3149112 read:2901248 written:0 al-writes:0 bm-writes:0 upper-pending:0 lower-pending:0 al-suspended:no blocked:no
2019-08-18T02:29:24.637883+08:00 exists -

Is this just visual issue ? Can I continue work with it ?

[deleteriousEffect]

Yes, this is a display bug, I have an idea of the cause.

It should clear up if you were to add another replica.