[lvm-devel] Aborting. LV mythinpool_tmeta is now incomplete
Zdenek Kabelac
zkabelac at redhat.com
Thu Apr 11 12:12:05 UTC 2019
Dne 11. 04. 19 v 13:49 Eric Ren napsal(a):
> Hi,
>
> Hi,
>
> I could recommend to orient towards the solution where the 'host' system
> provides some service for your containers - so container ask for action,
> service orchestrates the action on the system - and returns asked resource to
> the container.
>
>
> Right, it's all k8s, containerd, OCI runtime are doing.
>
>
> IMHO I don't see any other usable solution ATM - although many container
> developers seems to endlessly try to run these system commands from a
> container...
>
>
> Sorry, I don't make it clear. I mean we don't use lvm in container, we use
> thin pool on physical server, create thin LV, passthrough thin dm device into
> virtual machine (KATA VM, not cgroup&namespce-based container) as VM's rootfs.
>
Hi
So do you get 'partial' error on thin-pool activation on your physical server ?
Then you likely miss some PV on your system.
As that's the only way how lvm2 can give you this report - it cannot find all
required PVs for the VG - so you cannot activate without partial activation.
You should easily spot which PV is missing with -vvvv trace for
lvchange -ay
Regards
Zdenek
More information about the lvm-devel
mailing list