all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH storage v3 1/3] diskmanage: add mounted_paths
Date: Fri, 19 Aug 2022 17:01:19 +0200	[thread overview]
Message-ID: <20220819150121.1633021-2-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20220819150121.1633021-1-a.lauterer@proxmox.com>

returns a list of mounted paths with the backing devices

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
changes since
v2: added comment about return value
v1: dropped limit to /dev path, returning all mounted paths now

 PVE/Diskmanage.pm | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/PVE/Diskmanage.pm b/PVE/Diskmanage.pm
index 8ed7a8b..81df67f 100644
--- a/PVE/Diskmanage.pm
+++ b/PVE/Diskmanage.pm
@@ -499,6 +499,19 @@ sub mounted_blockdevs {
     return $mounted;
 }
 
+# returns hashmap of abs mount path -> first part of /proc/mounts (what)
+sub mounted_paths {
+    my $mounted = {};
+
+    my $mounts = PVE::ProcFSTools::parse_proc_mounts();
+
+    foreach my $mount (@$mounts) {
+	$mounted->{abs_path($mount->[1])} = $mount->[0];
+    };
+
+    return $mounted;
+}
+
 sub get_disks {
     my ($disks, $nosmart, $include_partitions) = @_;
     my $disklist = {};
-- 
2.30.2





  reply	other threads:[~2022-08-19 15:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 15:01 [pve-devel] [PATCH storage v3 0/3] disks: add checks, allow add_storage on other nodes Aaron Lauterer
2022-08-19 15:01 ` Aaron Lauterer [this message]
2022-08-19 15:01 ` [pve-devel] [PATCH storage v3 2/3] disks: die if storage name is already in use Aaron Lauterer
2022-08-19 15:01 ` [pve-devel] [PATCH storage v3 3/3] disks: allow add_storage for already configured local storage Aaron Lauterer
2022-09-05  9:50 ` [pve-devel] [PATCH storage v3 0/3] disks: add checks, allow add_storage on other nodes Dominik Csapak
2022-09-13  8:06   ` [pve-devel] applied-series: " Fabian Grünbichler

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=20220819150121.1633021-2-a.lauterer@proxmox.com \
    --to=a.lauterer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal