From: Eric Ren <renzhengeek@gmail.com>
To: Zdenek Kabelac <zkabelac@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>,
thornber@redhat.com, lvm-devel@redhat.com
Subject: Re: [linux-lvm] Aborting. LV mythinpool_tmeta is now incomplete
Date: Thu, 11 Apr 2019 19:26:22 +0800 [thread overview]
Message-ID: <CAKM4Aexm31mYW8WDeiZ4shCoysCcGjic8zV0XiVqEVZvKz-ecQ@mail.gmail.com> (raw)
In-Reply-To: <47346a29-e6c7-6e22-4360-2d07e2ec7be3@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
Hi Zdenek,
Thanks for your reply. The use case is for containerd snapshooter, yes, all
lvm setup is on host machine, creating thin LV for VM-based/KATA container
as rootfs.
For example:
https://github.com/containerd/containerd/pull/3136
and
https://github.com/containerd/containerd/pull/3022
So, we're evaluating such solution now~
Thanks,
Eric
On Thu, 11 Apr 2019 at 19:04, Zdenek Kabelac <zkabelac@redhat.com> wrote:
> Dne 11. 04. 19 v 2:27 Eric Ren napsal(a):
> > Hello list,
> >
> > Recently, we're exercising our container environment which uses lvm to
> manage
> > thin LVs, meanwhile we found a very strange error to activate the thin
> LV:
> >
>
>
> Hi
>
>
> The reason is very simple here - lvm2 does not work from containers.
> It's unsupported and if it partially works - it's a pure lucky case.
>
> ATM it's simply clear statement that lvm2 cannot be used from container
> simply
> because block layer is not namespaced.
>
> I'd give here long list of reason why it currently cannot work, but for
> now -
> you should focus on making all 'device-block' operation on you host - and
> pass
> results to container.
>
> Regards
>
> Zdenek
>
--
- Eric Ren
[-- Attachment #2: Type: text/html, Size: 2051 bytes --]
next prev parent reply other threads:[~2019-04-11 11:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 0:27 [linux-lvm] Aborting. LV mythinpool_tmeta is now incomplete Eric Ren
2019-04-11 10:01 ` Eric Ren
2019-04-11 11:21 ` [linux-lvm] [lvm-devel] " Zdenek Kabelac
2019-04-11 11:03 ` [linux-lvm] " Zdenek Kabelac
2019-04-11 11:26 ` Eric Ren [this message]
2019-04-11 11:32 ` Zdenek Kabelac
2019-04-11 11:49 ` Eric Ren
2019-04-11 12:12 ` Zdenek Kabelac
2019-04-11 13:09 ` Eric Ren
2019-04-11 13:13 ` Zdenek Kabelac
[not found] ` <CAKM4Aez9H=GuRLK0EDJTwpb7j34tCu1aY4dS5_L4saDGERestg@mail.gmail.com>
2019-04-11 17:33 ` Eric Ren
2019-04-12 10:05 ` [linux-lvm] [lvm-devel] " Zdenek Kabelac
2019-04-12 10:42 ` Eric Ren
2019-04-12 13:44 ` [linux-lvm] " Zdenek Kabelac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKM4Aexm31mYW8WDeiZ4shCoysCcGjic8zV0XiVqEVZvKz-ecQ@mail.gmail.com \
--to=renzhengeek@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=lvm-devel@redhat.com \
--cc=thornber@redhat.com \
--cc=zkabelac@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).