You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One resource turned into a bad situation during the night. After trying to remove (linstor r d) the resource on a node with an outdated state it is not possible to check status with drbdadm or drbdsetup on the primary node (satellite). While drbdadm times out, drbdsetup just freezes.
root@de-fra-node11:/# drbdadm status pvc-976cacaa-af84-4398-814d-d4745288e81a
Command 'drbdsetup status pvc-976cacaa-af84-4398-814d-d4745288e81a' did not terminate within 5 seconds
root@de-fra-node11:/# drbdsetup show pvc-976cacaa-af84-4398-814d-d4745288e81a
All other resources on the node work just fine and drbdadm + drbdsetup work as expected.
One resource turned into a bad situation during the night. After trying to remove (linstor r d) the resource on a node with an outdated state it is not possible to check status with drbdadm or drbdsetup on the primary node (satellite). While drbdadm times out, drbdsetup just freezes.
All other resources on the node work just fine and drbdadm + drbdsetup work as expected.
This is how the resources looks like in Linstor:
drbdmon still shows the resource:
We are using Piraeus with Linstor 1.20 and DRBD 1.9.12 on Ubuntu 20.04 LTS. Before DRBD 1.9.12 we never saw a freezing drbdsetup call.
We experienced the same situation with another resource. The only way to get out of this situation was to reboot the node.
The text was updated successfully, but these errors were encountered: