all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Aaron Lauterer <a.lauterer@proxmox.com>
Subject: Re: [pve-devel] [PATCH storage 1/3] diskmanage: add mounted_paths
Date: Thu, 14 Jul 2022 13:13:36 +0200	[thread overview]
Message-ID: <05875cc8-fa13-23f6-ce53-c0980e1a530f@proxmox.com> (raw)
In-Reply-To: <20220713104758.651614-2-a.lauterer@proxmox.com>

comment inline

On 7/13/22 12:47, Aaron Lauterer wrote:
> returns similar values as mounted_blockdevs, but uses the mounted path
> as key and the blockdev path as value
> 
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
> used for the Directory check in patch 2
> 
>   PVE/Diskmanage.pm | 13 +++++++++++++
>   1 file changed, 13 insertions(+)
> 
> diff --git a/PVE/Diskmanage.pm b/PVE/Diskmanage.pm
> index 8ed7a8b..c5c20de 100644
> --- a/PVE/Diskmanage.pm
> +++ b/PVE/Diskmanage.pm
> @@ -499,6 +499,19 @@ sub mounted_blockdevs {
>       return $mounted;
>   }
>   
> +sub mounted_paths {
> +    my $mounted = {};
> +
> +    my $mounts = PVE::ProcFSTools::parse_proc_mounts();
> +
> +    foreach my $mount (@$mounts) {
> +	next if $mount->[0] !~ m|^/dev/|;

does it really make sense here to filter by /dev/ ?
for 'mounted_blockdevs' it makes sense since we want to have
the mounted 'block devices' but here we talk about 'paths'
and /sys,/proc, etc are paths too, so you could simply omit that check

> +	$mounted->{abs_path($mount->[1])} = $mount->[0];
> +    };
> +
> +    return $mounted;
> +}
> +
>   sub get_disks {
>       my ($disks, $nosmart, $include_partitions) = @_;
>       my $disklist = {};




  reply	other threads:[~2022-07-14 11:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 10:47 [pve-devel] [PATCH storage 0/3] disks: add checks, allow add_storage on other nodes Aaron Lauterer
2022-07-13 10:47 ` [pve-devel] [PATCH storage 1/3] diskmanage: add mounted_paths Aaron Lauterer
2022-07-14 11:13   ` Dominik Csapak [this message]
2022-07-14 11:37     ` Aaron Lauterer
2022-07-13 10:47 ` [pve-devel] [PATCH storage 2/3] disks: die if storage name is already in use Aaron Lauterer
2022-07-14 11:13   ` Dominik Csapak
2022-07-14 12:12     ` Fabian Ebner
2022-07-14 12:30       ` Dominik Csapak
2022-07-13 10:47 ` [pve-devel] [PATCH storage 3/3] disks: allow add_storage for already configured local storage Aaron Lauterer
2022-07-14 11:23   ` Dominik Csapak

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=05875cc8-fa13-23f6-ce53-c0980e1a530f@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=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