Hello Timm,
I had exactly the same problem a few weeks ago. It pissed me off quite a
bit, but I made myself a reason.
My workaround is not to define the volume pool anymore. The domains are
able to use any volume anyway, even when not part of any pool.
I use custom hooks to activate and deactivate LVs.
Hope that helps,
Guy
Le 14/02/2020 à 11:28, Timm Wunderlich a écrit :> dear all,
>
> i have a problem with clustered lvm storage and the "logical"
storage
> driver, perhaps someone has a suggestion.
>
> i have a clustered lvm (lvmlockd, not clvm) with 4 hosts running.
>
> when i start the storage on a host it activates all volumes in the whole
> volume group. then i cannot start the storage on other hosts because all
> volumes are already activated on one host.
>
> if i then deactivate all volumes in the started pool i can start the
> pool on other hosts. but then i have to manually activate the volume if
> i want to start the domain.
>
> it would be great if the logical pool driver would only activate the
> volume of a domain at domain start and not on pool start.
>
> does anybody have a workaround for this or any suggestions for me? do
> you think i should open an issue on it?
>
> Regards,
> Timm
>
>
