public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH storage] Diskmanage: check for extended partitions
Date: Tue, 3 May 2022 13:39:15 +0200	[thread overview]
Message-ID: <20220503133915.3eb8d77a@rosa.proxmox.com> (raw)
In-Reply-To: <20220503110847.2396527-1-d.csapak@proxmox.com>

On Tue,  3 May 2022 13:08:47 +0200
Dominik Csapak <d.csapak@proxmox.com> wrote:

> those would not get assinged a usage and thus appear in the list
> when we want to select a partition (e.g. for creating a zpool)
> 
> since we cannot do anything with such a  partition, return the usage
> 'Extended Partition' for these.
> 
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
>  PVE/Diskmanage.pm | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/PVE/Diskmanage.pm b/PVE/Diskmanage.pm
> index d67cc6b..f693d00 100644
> --- a/PVE/Diskmanage.pm
> +++ b/PVE/Diskmanage.pm
> @@ -647,6 +647,8 @@ sub get_disks {
>  		    if $parttype eq 'c12a7328-f81f-11d2-ba4b-00a0c93ec93b';
>  		return 'ZFS reserved'
>  		    if $parttype eq '6a945a3b-1dd2-11b2-99a6-080020736631';
> +		return 'Extended Partition'
> +		    if $parttype eq '0x5';
This looks like a MBR partitiontype (both the length and the concept of
extended partition seem MBR-related) - Do we want to support MBR disks?
(we do not in the installer and when initializing a new disk)
Any pointer to where this could be needed?

Really meant as an expression of my confusion - am fine if we want to
support this and the patch LGTM.

> ..snip..




  reply	other threads:[~2022-05-03 11:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 11:08 Dominik Csapak
2022-05-03 11:39 ` Stoiko Ivanov [this message]
2022-05-03 11:41   ` 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=20220503133915.3eb8d77a@rosa.proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=d.csapak@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal