From: Ben Dailey <bdailey@bhmsd.org>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] vma extract force flag
Date: Tue, 30 Apr 2024 14:06:23 -0400 [thread overview]
Message-ID: <CAD5+3sNcTWntTucmByfdFT6OeMjG73PhfS6eq8_zc0nSNB_7Ww@mail.gmail.com> (raw)
In-Reply-To: <bd8d3d1c-9bb3-4d08-905f-541c9ecfe9e5@proxmox.com>
The hope would be to get the benefits of nop-write from the underlying ZFS
filesystem therefore increasing performance and reducing snapshot size
without the need for deduplication being enabled. I have often found large
deletes on ZFS to sometimes not be very performant as well, especially if
deduplication is enabled.
https://openzfs.org/wiki/Features#nop-write
Praise the Lord!
Ben Dailey
Associate Technology Director
Bluffton-Harrison MSD
bdailey@bhmsd.org
On Tue, Apr 30, 2024 at 4:26 AM Fiona Ebner <f.ebner@proxmox.com> wrote:
> Hi,
>
> Am 24.04.24 um 22:44 schrieb Ben Dailey:
> > I would like to keep extracted backups on an NFS server backed with ZFS
> and
> > retain the benefits of differential snapshots and it would be helpful to
> > have the vma extract replace the previous backups directly.
>
> why not just remove the previously extracted archive and then extract
> the new archive?
>
> Best Regards,
> Fiona
>
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-04-30 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 20:44 Ben Dailey
2024-04-30 8:26 ` Fiona Ebner
2024-04-30 18:06 ` Ben Dailey [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=CAD5+3sNcTWntTucmByfdFT6OeMjG73PhfS6eq8_zc0nSNB_7Ww@mail.gmail.com \
--to=bdailey@bhmsd.org \
--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