all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Michael Köppl" <m.koeppl@proxmox.com>
To: Christoph Heiss <c.heiss@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-installer v2 3/6] close #5887: add sanity check for LVM swapsize and maxroot
Date: Tue, 27 May 2025 18:19:06 +0200	[thread overview]
Message-ID: <da8d0f52-e515-4941-ab1c-e2ce2fcfa8d0@proxmox.com> (raw)
In-Reply-To: <9a5036b0-8549-47b8-84c4-6f4d8d9c9a84@proxmox.com>

Ping, still applies

On 5/9/25 13:07, Michael Köppl wrote:
> On 5/6/25 13:48, Christoph Heiss wrote:
>> After testing this change and thinking about the maxroot change again,
>> $hdsize / 4 doesn't really make sense. E.g. for an (unrealistically
>> small, but still) disk of 8 GiB; if its unset, pve-root will be ~6.5 GiB
>> in size, with the limit of 2 GiB, the installation fails due to
>> ENOSPACE.
>>
>> The default calculations try really hard to make installations possible
>> even on small disks, in Proxmox/Install.pm:create_lvm_volumes()
>>
>> So I'm not sure if we really should restrict it that much, or rather
>> relax it in the documentation.
> 
> Thought a bit about this. I agree that the sanity check should not
> entirely stop users from creating setups that would work. An alternative
> approach might be not to enforce the maxroot limit of $hdsize / 4 for
> smaller disks. create_lvm_volumes() considers 12 GiB to be small, if I'm
> not mistaken, and basically does a best-effort install. I'm not sure if
> I like setting such an arbitrary limit for a sanity check, though. It
> makes the sanity check intransparent if users cannot configure a root
> volume size greater than 4 GiB if their hdsize is 16 GiB, but at the
> same time are free to set it to 6 GiB if the hdsize is 8 GiB. What do
> you think?
> 
> Another alternative might be to simply display a warning that doesn't
> stop users from installing, i.e. "Recommended maximum root volume size
> is hdsize / 4".
> 
> In both cases the documentation should be updated to reflect that.
> 
> 
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> 
> 



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-05-27 16:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29 14:09 [pve-devel] [PATCH installer v2 0/6] add early disk and network sanity checks Michael Köppl
2025-04-29 14:09 ` [pve-devel] [PATCH pve-installer v2 1/6] auto: add early answer file sanity check for RAID configurations Michael Köppl
2025-04-29 14:09 ` [pve-devel] [PATCH pve-installer v2 2/6] move RAID setup checks to RAID level enum implementations Michael Köppl
2025-04-29 14:09 ` [pve-devel] [PATCH pve-installer v2 3/6] close #5887: add sanity check for LVM swapsize and maxroot Michael Köppl
2025-05-06 11:48   ` Christoph Heiss
2025-05-09 11:07     ` Michael Köppl
2025-05-27 16:19       ` Michael Köppl [this message]
2025-04-29 14:09 ` [pve-devel] [PATCH pve-installer v2 4/6] auto: add check for duplicate disks in answer file Michael Köppl
2025-04-29 14:09 ` [pve-devel] [PATCH pve-installer v2 5/6] common: add more descriptive errors for invalid network configs Michael Köppl
2025-04-29 14:09 ` [pve-devel] [RFC PATCH pve-installer v2 6/6] common: add checks for valid subnet mask and IPv4 address within subnet Michael Köppl
2025-05-06  9:21   ` Christoph Heiss
2025-05-09  8:51     ` Michael Köppl

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=da8d0f52-e515-4941-ab1c-e2ce2fcfa8d0@proxmox.com \
    --to=m.koeppl@proxmox.com \
    --cc=c.heiss@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