Robert Altnoeder

There were plans that a Controller would delete resources immediately if Satellites had never been informed that the resource exists (because then the Satellite obviously cannot have remains of the...

Renaming resources is virtually impossible, first due to internal constraints in LINSTOR (it would have to keep both resource names until the resource was successfully renamed everywhere, but the data...

I designed the software (LINSTOR), and the main priority when the project was started in 2016 was better reliability and maintainability, because the typical use case for DRBD is for...

The strong coupling between resource names in LINSTOR, DRBD and the backing volumes exists for maintainability. Most administrators are already overwhelmed with using the system as it is, and it...

Resource groups are not required to be associated with a storage pool, so they cannot report statistics about the free or total capacity of "the resource group". A resource group...

That's the problem, you would probably get different data every time you run it, not useful for anything.

Simple scenario: I have a resource group `profile` that is configured to use storage pool `main`, and there are currently 3 resources associated with it, which all are in storage...

"External command timed out" means that the `lvremove` utility was stuck for longer than what LINSTOR's timeout for running external commands allows (the default is 45 seconds). The reason for...

The original error in this issue said: ``` Resource definition 'vdd_rSc' marked for deletion. The given node name 'vdd_rSc' is invalid. ``` That looks like some piece of code mixing...

There are known problems in the reconnector that prevent the controller from reconnecting automatically. Once the affected parts are redesigned and reimplemented, it should be able to reliably reconnect automatically....