[DRBD-user] No quorum on UpToDate devices

[Baji Zsolt]

Helo,

blocked:upper - Your physical device (HDD/SSD) is blocked, can not be 
accessed. You need to solve this problem

Or sometimes the drbd kernel process for this drbd device stop to work. 
Check it with dmesg, you  can find log from some frozed drbd process. 
For this situation You can only restart the server.

Zsolt

2023. 03. 15. 17:27 keltezéssel, kvaps írta:

> Hi, any idea why drbd can lose their quorum? All the replicas are 
> UpToDate:
>
> root at kube-node-14:/# drbdsetup status 
> pvc-2ba7ccd7-e92c-4c92-be8e-6e55c9a0840d
> pvc-2ba7ccd7-e92c-4c92-be8e-6e55c9a0840d role:Primary
>   disk:Diskless
>   kube-node-4 role:Secondary
>     peer-disk:UpToDate
>   kube-node-6 role:Secondary
>     peer-disk:UpToDate
>
> root at kube-node-6:/# drbdsetup status 
> pvc-2ba7ccd7-e92c-4c92-be8e-6e55c9a0840d
> pvc-2ba7ccd7-e92c-4c92-be8e-6e55c9a0840d role:Secondary suspended:quorum
>   disk:UpToDate quorum:no blocked:upper
>   kube-node-14 role:Primary
>     peer-disk:Diskless
>   kube-node-4 role:Secondary
>     peer-disk:UpToDate
>
> root at kube-node-4:/# drbdsetup status 
> pvc-2ba7ccd7-e92c-4c92-be8e-6e55c9a0840d
> pvc-2ba7ccd7-e92c-4c92-be8e-6e55c9a0840d role:Secondary suspended:quorum
>   disk:UpToDate quorum:no blocked:upper
>   kube-node-14 role:Primary
>     peer-disk:Diskless
>   kube-node-6 role:Secondary
>     peer-disk:UpToDate
>
>
> Best Regards,
> Andrei Kvapil
>
> _______________________________________________
> Star us on GITHUB:https://github.com/LINBIT
> drbd-user mailing list
> drbd-user at lists.linbit.com
> https://lists.linbit.com/mailman/listinfo/drbd-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20230315/c8b059b1/attachment.htm>