From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH-SERIES storage 0/3] small fixes towards btrfs incremental export/import
Date: Sun, 6 Apr 2025 21:19:19 +0200 [thread overview]
Message-ID: <524ca0a9-eec6-48a2-911f-4680e2cc5507@proxmox.com> (raw)
In-Reply-To: <20250221154111.73194-1-f.ebner@proxmox.com>
Am 21.02.25 um 16:41 schrieb Fiona Ebner:
> I noticed that btrfs incremental export/import does not currently work
> when testing Maximiliano's series[0]. While these fixes don't make it
> work either, they should make life easier for a future developer
> actually tackling that feature.
>
> [0]: https://lore.proxmox.com/pve-devel/20250219111740.200819-1-m.sandoval@proxmox.com/
>
> Fiona Ebner (3):
> volume export: fix handling of snapshot list
> btrfs: volume import: fix check for presence of base snapshot
> btrfs: volume export: fix command for incremental stream
>
> src/PVE/CLI/pvesm.pm | 2 +-
> src/PVE/Storage/BTRFSPlugin.pm | 4 +++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
applied series, third patch had some context changes that weren't hard to
resolve, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-04-06 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 15:41 [pve-devel] " Fiona Ebner
2025-02-21 15:41 ` [pve-devel] [PATCH storage 1/3] volume export: fix handling of snapshot list Fiona Ebner
2025-02-21 15:41 ` [pve-devel] [PATCH storage 2/3] btrfs: volume import: fix check for presence of base snapshot Fiona Ebner
2025-02-21 15:41 ` [pve-devel] [PATCH storage 3/3] btrfs: volume export: fix command for incremental stream Fiona Ebner
2025-04-06 19:19 ` 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=524ca0a9-eec6-48a2-911f-4680e2cc5507@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 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