From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox/proxmox-backup v3] restore files from pxar sparsely
Date: Tue, 9 Feb 2021 10:36:58 +0100 [thread overview]
Message-ID: <20210209093700.30531-1-d.csapak@proxmox.com> (raw)
to be able to restore containers with big sparse files
ideally(?) we would save hole information directly in the pxar archive
and not even use zero chunks, so that we can have smaller
pxar archives, and accurately restore sparse files like they were before
for now, restore all files sparsely
i am not sure if v2 or this is better, since before we could
restore if truncate did not work, now we fail
but we have probably less io.
changes from v2:
* always sparse copy and truncate after
changes from RFC:
* drop the zero module of proxmox, rust can generate fast code by itself
proxmox:
Dominik Csapak (1):
proxmox: add sparse_copy(_async) to tools::io
proxmox/src/tools/io/mod.rs | 70 +++++++++++++++++++++++++++++++++++++
1 file changed, 70 insertions(+)
proxmox-backup:
Dominik Csapak (1):
pxar/extract: if possible create files sparesly
src/pxar/extract.rs | 24 +++++++++++++++++++++---
1 file changed, 21 insertions(+), 3 deletions(-)
--
2.20.1
next reply other threads:[~2021-02-09 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 9:36 Dominik Csapak [this message]
2021-02-09 9:36 ` [pbs-devel] [PATCH proxmox v3 1/1] proxmox: add sparse_copy(_async) to tools::io Dominik Csapak
2021-02-09 9:37 ` [pbs-devel] [PATCH proxmox-backup v3 1/1] pxar/extract: if possible create files sparesly Dominik Csapak
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=20210209093700.30531-1-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pbs-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