From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: applied: [PATCH v2 docs] storage: note that qcow2 internal snapshots are inefficient
Date: Wed, 1 Apr 2026 01:47:47 +0200 [thread overview]
Message-ID: <177500080335.1379592.1525279812523628708.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260323110642.51984-1-f.ebner@proxmox.com>
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
prev parent reply other threads:[~2026-03-31 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 11:06 Fiona Ebner
2026-03-23 11:59 ` Maximiliano Sandoval
2026-03-31 23:47 ` Thomas Lamprecht [this message]
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=177500080335.1379592.1525279812523628708.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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