From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id E0F411FF0A8 for ; Sat, 17 Oct 2026 22:29:03 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 9A65421481; Sat, 17 Oct 2026 22:29:02 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Shannon Sterz Subject: applied: [PATCH proxmox] installer-types: align documentation of hdsize for btrfs with lvm & zfs Date: Sat, 17 Oct 2026 22:28:41 +0200 Message-ID: <179226891335.3581685.9262300324953970380.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260713092234.73883-1-s.sterz@proxmox.com> References: <20260713092234.73883-1-s.sterz@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1792268932637 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.488 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: UOMRB4YUQ3V6XDFYR5H5XV4UONKYIR2X X-Message-ID-Hash: UOMRB4YUQ3V6XDFYR5H5XV4UONKYIR2X X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 13 Jul 2026 11:22:34 +0200, Shannon Sterz wrote: > to avoid confusion. the hdsize is used to determine how much space is > available for partitioning. it is not the size of the btrfs partition > itself. the `LvmOptions` and `ZfsOptions` already specify this > correctly, so align the documentation here to avoid confusion. Applied, thanks! [1/1] installer-types: align documentation of hdsize for btrfs with lvm & zfs commit: 5e191fc05fa78252199c27702a1984fffd54d408