From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 46E4167B42 for ; Wed, 13 Jan 2021 13:20:13 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3E28611AA3 for ; Wed, 13 Jan 2021 13:20:13 +0100 (CET) Received: from dev.dominic.proxmox.com (212-186-127-178.static.upcbusiness.at [212.186.127.178]) by firstgate.proxmox.com (Proxmox) with ESMTP id 19A7711A99 for ; Wed, 13 Jan 2021 13:20:09 +0100 (CET) Received: by dev.dominic.proxmox.com (Postfix, from userid 0) id ECBF02296E; Wed, 13 Jan 2021 13:20:08 +0100 (CET) From: =?UTF-8?q?Dominic=20J=C3=A4ger?= To: pve-devel@lists.proxmox.com Date: Wed, 13 Jan 2021 13:19:54 +0100 Message-Id: <20210113121954.156264-1-d.jaeger@proxmox.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 1 AWL -0.370 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods KHOP_HELO_FCRDNS 0.4 Relay HELO differs from its IP's reverse DNS NO_DNS_FOR_FROM 0.379 Envelope sender has no MX or A DNS records SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [lvmplugin.pm] Subject: [pve-devel] [PATCH storage] lvm: Fix #3159: Show RAID LVs as storage content X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jan 2021 12:20:13 -0000 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 Signed-off-by: Dominic Jäger --- PVE/Storage/LVMPlugin.pm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/PVE/Storage/LVMPlugin.pm b/PVE/Storage/LVMPlugin.pm index 73e8e48..df49b76 100644 --- a/PVE/Storage/LVMPlugin.pm +++ b/PVE/Storage/LVMPlugin.pm @@ -446,7 +446,8 @@ sub list_images { next if $scfg->{tagged_only} && !&$check_tags($info->{tags}); - next if $info->{lv_type} ne '-'; + # Allow mirrored and RAID LVs + next if $info->{lv_type} !~ m/^[-mMrR]$/; my $volid = "$storeid:$volname"; -- 2.20.1