From: "DERUMIER, Alexandre via pve-devel" <pve-devel@lists.proxmox.com>
To: "joao.sousa@eurotux.com" <joao.sousa@eurotux.com>,
"pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
Subject: Re: [pve-devel] [PATCH-SERIES v6 pve-storage/qemu-server/pve-qemu] add external qcow2 snapshot support
Date: Thu, 12 Jun 2025 11:33:18 +0000 [thread overview]
Message-ID: <mailman.347.1749728041.395.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <8cbed06bbe3db00e96670dec1e240123b946a917.camel@groupe-cyllene.com>
[-- Attachment #1: Type: message/rfc822, Size: 14128 bytes --]
From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "joao.sousa@eurotux.com" <joao.sousa@eurotux.com>, "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH-SERIES v6 pve-storage/qemu-server/pve-qemu] add external qcow2 snapshot support
Date: Thu, 12 Jun 2025 11:33:18 +0000
Message-ID: <a7185aa585b414710be6e09729adda57ed3787b8.camel@groupe-cyllene.com>
> > Later on, I'd like to contribute to a version which
> > enables thin provisioned snapshots.
>>For thin provision, I have done prelimary work in september 2024
>>(check
>>the pve-devel mailing),
>>but I was waiting to have first the snapshot finished.
here the patch series:
https://lists.proxmox.com/pipermail/pve-devel/2024-August/065201.html
The idea is to create a lvm volume smaller than the real qcow2 size,
qemu is sending an event when the used space reach a threshold,
then a daemon should resize the lvm volume by increment.(1GB for
example),
until the next threshold reach....
The only complex thing is to manage some kind of queue in this daemon
and manage
lvm cluster lock, as we can't resize multiple lvm volume at the same
time.
(Not sure if it need a central daemon, or a distributed daemon on each
node with a shared queue in /etc/pve ...)
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-06-12 11:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 7:55 Alexandre Derumier via pve-devel
2025-06-05 13:53 ` Fiona Ebner
2025-06-05 14:08 ` DERUMIER, Alexandre via pve-devel
[not found] ` <0aa862ab988ff9df50f4637f3712f137f23c34c2.camel@groupe-cyllene.com>
2025-06-05 14:19 ` Fiona Ebner
2025-06-06 10:17 ` joao.sousa via pve-devel
2025-06-10 8:54 ` Fiona Ebner
2025-06-11 21:28 ` joao.sousa via pve-devel
[not found] ` <5sqpzsnyzmfvvoco3ilo6tg3pcpomhle7h5dsnmbsbdjobpr5a@rqfsbsas36e2>
2025-06-12 7:02 ` DERUMIER, Alexandre via pve-devel
2025-06-12 8:12 ` Fiona Ebner
2025-06-13 10:25 ` joao.sousa via pve-devel
[not found] ` <zwkygc6va6jmieho2h7gqsx4idrgrxvd7et2kfbi3vyddhjk7c@kfiwufb7auvv>
2025-06-16 8:34 ` Fiona Ebner
[not found] ` <8cbed06bbe3db00e96670dec1e240123b946a917.camel@groupe-cyllene.com>
2025-06-12 11:33 ` DERUMIER, Alexandre via pve-devel [this message]
[not found] ` <a7185aa585b414710be6e09729adda57ed3787b8.camel@groupe-cyllene.com>
2025-06-13 16:42 ` joao.sousa--- via pve-devel
[not found] ` <qss36oltvd4gz5tiss7dqono5h2zmsgwmodj4cqkroboizypwj@kbyz3mymh75a>
2025-06-16 5:50 ` DERUMIER, Alexandre via pve-devel
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=mailman.347.1749728041.395.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=alexandre.derumier@groupe-cyllene.com \
--cc=joao.sousa@eurotux.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