From: Zdenek Kabelac <zkabelac@redhat.com>
To: Eric Ren <renzhengeek@gmail.com>,
lvm-devel@redhat.com, thornber@redhat.com,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Aborting. LV mythinpool_tmeta is now incomplete
Date: Thu, 11 Apr 2019 13:03:56 +0200 [thread overview]
Message-ID: <47346a29-e6c7-6e22-4360-2d07e2ec7be3@redhat.com> (raw)
In-Reply-To: <CAKM4AewbcVR1x0cK8hWLCRxb1BzDd-F+WeK6ObUmB35N1HTqOA@mail.gmail.com>
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
next prev parent reply other threads:[~2019-04-11 11:03 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 ` Zdenek Kabelac [this message]
2019-04-11 11:26 ` [linux-lvm] " Eric Ren
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=47346a29-e6c7-6e22-4360-2d07e2ec7be3@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=lvm-devel@redhat.com \
--cc=renzhengeek@gmail.com \
--cc=thornber@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).