Moritz Wanzenböck

There may be a mount option that does that, but I am not sure. Data corruption is a serious issue, so if you could please attach an sos-report (linstor sos-report...

> Is there any "easy" way for the operator to recreate automagically the linstor resources associated with this pvc such that I can then bind it to an existing workload....

Having thought some more about it: Would it make sense to use a custom taint instead of a node label? So `piraeus.io/node-removal: NoSchedule`? That way we would also automatically prevent...

I think the satellite needs to tolerate it's own taint.

Ok, sorry for the long delay. I played around with this PR a bit more, but I wasn't really happy with the general workflow. There is some improvement coming on...

> Regarding above: How would volumes be handled which only have 1 replica? Would they still be migrated? Yes. When the evacuation is triggered, such a resource would have 2...

First idea was just the resync saturating the network. I believe the default `c-max-rate` (i.e. max resync speed) is around 100MB/s, so if more than 9 resources need to sync...

Two settings you can play with: ```yaml apiVersion: piraeus.io/v1 kind: LinstorCluster metadata: name: linstorcluster spec: properties: - name: DrbdOptions/PeerDevice/c-max-rate value: "102400" # I believe the unit is kilobits/s here -...

> auto-resync-after-disable seems like exactly what I'd need, assuming the issue is indeed what we think here. I tried setting it on the LinstorCluster resource as above, but that didn't...

I suggest you open an issue over at https://github.com/LINBIT/drbd, ideally with the full kernel log