From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 569B21FF13A for ; Wed, 01 Apr 2026 01:48:00 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 5B1469D6D; Wed, 1 Apr 2026 01:48:27 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Fiona Ebner Subject: applied: [PATCH v2 docs] storage: note that qcow2 internal snapshots are inefficient Date: Wed, 1 Apr 2026 01:47:47 +0200 Message-ID: <177500080335.1379592.1525279812523628708.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260323110642.51984-1-f.ebner@proxmox.com> References: <20260323110642.51984-1-f.ebner@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: 1775000817325 X-SPAM-LEVEL: Spam detection results: 0 AWL -1.502 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 1 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 1 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 1 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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: IR56OTL6UXO2JH6WECP5JTON3ZAOEV3Z X-Message-ID-Hash: IR56OTL6UXO2JH6WECP5JTON3ZAOEV3Z 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, 23 Mar 2026 12:06:25 +0100, Fiona Ebner wrote: > It's a commonly reported issue, often also in the enterprise support, > that taking or removing snapshots of large qcow2 files on file-based > network storages can take a very long time. Add a note about this > limitation. > > Not 100% sure if this is the best place for this info, but it's not the wrong place, it's central and from top of my head I do not have a better idea, so probably fine.. Applied, thanks! [1/1] storage: note that qcow2 internal snapshots are inefficient commit: 0bb63fb9b322a33d0f2f28cc49b2dbb9adad5c48