From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Dominic Jäger" <d.jaeger@proxmox.com>
Subject: [pve-devel] applied: [PATCH storage] lvm: Fix #3159: Show RAID LVs as storage content
Date: Tue, 26 Jan 2021 19:20:04 +0100 [thread overview]
Message-ID: <1eca9bb4-bf0b-7ac3-c301-6df3a4e4dc78@proxmox.com> (raw)
In-Reply-To: <20210113121954.156264-1-d.jaeger@proxmox.com>
On 13.01.21 13:19, Dominic Jäger wrote:
> LVM RAID logical volumes (including mirrors) can be valid disk images, so they
> should show up in storage content listings (for example pvesm list).
>
> Including LV types is safer than excluding, especially because of possible
> additional types in the future.
>
> Co-developed-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> Signed-off-by: Dominic Jäger <d.jaeger@proxmox.com>
> ---
> PVE/Storage/LVMPlugin.pm | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
>
applied, thanks!
prev parent reply other threads:[~2021-01-26 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 12:19 [pve-devel] " Dominic Jäger
2021-01-26 18:20 ` Thomas Lamprecht [this message]
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=1eca9bb4-bf0b-7ac3-c301-6df3a4e4dc78@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.jaeger@proxmox.com \
--cc=pve-devel@lists.proxmox.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