From mboxrd@z Thu Jan 1 00:00:00 1970 References: <47346a29-e6c7-6e22-4360-2d07e2ec7be3@redhat.com> <7839ff52-18e5-6a95-9a2a-12ea73457700@redhat.com> From: Zdenek Kabelac Message-ID: <62151b2e-c21a-177e-f66b-e2e08857be17@redhat.com> Date: Thu, 11 Apr 2019 14:12:05 +0200 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [linux-lvm] Aborting. LV mythinpool_tmeta is now incomplete Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="utf-8"; format="flowed" To: LVM2 development , Eric Ren , Zdenek Kabelac Cc: thornber@redhat.com, LVM general discussion and development 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zdenek Kabelac Date: Thu, 11 Apr 2019 14:12:05 +0200 Subject: Aborting. LV mythinpool_tmeta is now incomplete In-Reply-To: References: <47346a29-e6c7-6e22-4360-2d07e2ec7be3@redhat.com> <7839ff52-18e5-6a95-9a2a-12ea73457700@redhat.com> Message-ID: <62151b2e-c21a-177e-f66b-e2e08857be17@redhat.com> List-Id: To: lvm-devel@redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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