public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Robert Obkircher <r.obkircher@proxmox.com>
Subject: Re: [pbs-devel] [PATCH v2 proxmox-backup 0/5] fix: #3847 pipe from STDIN to proxmox-backup-client
Date: Thu, 8 Jan 2026 11:44:15 +0100	[thread overview]
Message-ID: <32a89cb5-763b-4489-8f3f-69a4e138faba@proxmox.com> (raw)
In-Reply-To: <20251219161850.244154-1-r.obkircher@proxmox.com>

Patches look promising already, great work! Huge improvement since the 
previous version of the patches.

Left some comments on individual patches, but nothing big so far.

On 12/19/25 5:18 PM, Robert Obkircher wrote:
> Add support for commands like:
>      ssh host cmd | proxmox-backup-client backup data.img:/dev/stdin
>      proxmox-backup-client backup a.img:<(mysqldump) b.img:<(pgdump)
> 
> Changes since v1:
> - use mremap+ftruncate instead of write_all_at
> - make the size API parameter optional instead of using 0
> - use an enum to represent fixed/dynamic chunk size in UploadOptions
> - alias "-" to "/dev/stdin"
> - split changes into separate commits
> 
> This does not yet need a detailed review, but let me know if anything
> looks completely off.
> 
> I'm still planning on writing some proper tests for the backend.
> That may involve moving the resizing logic to a type like
> proxmox_sys::mmap::Mmap, so it can be tested in isolation.
> 
> Christian Ebner previously suggested defining a trait for the
> FixedIndexWriter, with separate implementations for known and unknown
> size. I'm not sure if this is still necessary, because the changes are
> already much more isolated. Should I still introduce such a trait?

No, the current implementation really does not call for that at all.

> 
> 
> Robert Obkircher (5):
>    fix #3847: datastore: support writing fidx files of unknown size
>    fix #3847: api: backup: make fixed index file size optional
>    fix #3847: client: support fifo pipe inputs for images
>    fix #3847: client: treat minus sign as stdin
>    DO NOT MERGE: test script for reference
> 
>   pbs-client/src/backup_writer.rs   | 37 ++++++++----
>   pbs-datastore/src/datastore.rs    |  2 +-
>   pbs-datastore/src/fixed_index.rs  | 98 +++++++++++++++++++++++++++++--
>   proxmox-backup-client/src/main.rs | 37 ++++++++----
>   src/api2/backup/environment.rs    |  8 ++-
>   src/api2/backup/mod.rs            |  4 +-
>   src/server/push.rs                | 13 ++--
>   test-pipes.sh                     | 68 +++++++++++++++++++++
>   8 files changed, 227 insertions(+), 40 deletions(-)
>   create mode 100755 test-pipes.sh
> 



_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


      parent reply	other threads:[~2026-01-08 11:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 16:18 Robert Obkircher
2025-12-19 16:18 ` [pbs-devel] [PATCH v2 proxmox-backup 1/5] fix #3847: datastore: support writing fidx files of unknown size Robert Obkircher
2026-01-08 10:44   ` Christian Ebner
2025-12-19 16:18 ` [pbs-devel] [PATCH v2 proxmox-backup 2/5] fix #3847: api: backup: make fixed index file size optional Robert Obkircher
2025-12-19 16:18 ` [pbs-devel] [PATCH v2 proxmox-backup 3/5] fix #3847: client: support fifo pipe inputs for images Robert Obkircher
2026-01-08 10:44   ` Christian Ebner
2025-12-19 16:18 ` [pbs-devel] [PATCH v2 proxmox-backup 4/5] fix #3847: client: treat minus sign as stdin Robert Obkircher
2025-12-19 16:18 ` [pbs-devel] [PATCH v2 proxmox-backup 5/5] DO NOT MERGE: test script for reference Robert Obkircher
2026-01-08 10:44 ` Christian Ebner [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=32a89cb5-763b-4489-8f3f-69a4e138faba@proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=r.obkircher@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal