From: Savely Krasovsky <git@krasovs.ky>
To: Christian Ebner <c.ebner@proxmox.com>
Cc: pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup 0/2] fix #7606: verify: s3: handle transient fetch errors and add retry
Date: Tue, 29 Sep 2026 11:14:39 +0200 [thread overview]
Message-ID: <20260929091439.579314-1-git@krasovs.ky> (raw)
In-Reply-To: <20260903121557.420018-1-c.ebner@proxmox.com>
Hi Christian,
Do you have an update on the status of this series? Is there anything
still needed before it can be merged?
I'm running PBS 4.2.6-1 with an S3-backed datastore on Backblaze B2. A
single backup is over 1 TB, and I'm seeing errors like this on every
verification run:
can't verify chunk, load failed - error reading a body from connection
The latest verification job ran for 48 hours and 26 minutes before
finishing with "verification failed". It reported four such failures:
three while checking a file backup and one while checking a VM disk.
There were no checksum mismatch errors in the logs.
With backups this large, rerunning verification takes a long time and
requires a lot of S3 reads, only to hit similar errors again. Retrying
these transient failures would be very helpful for this workload.
Please let me know if any additional logs or details would help.
Thanks,
Savely
next prev parent reply other threads:[~2026-09-29 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 12:15 [PATCH proxmox-backup 0/2] fix #7606: verify: s3: handle transient fetch errors and add retry Christian Ebner
2026-09-03 12:15 ` [PATCH proxmox-backup 1/2] fix #7606: verify: s3: handle transient chunk load errors Christian Ebner
2026-09-03 12:15 ` [PATCH proxmox-backup 2/2] verify: s3: retry on transient response body collection errors Christian Ebner
2026-09-29 9:14 ` Savely Krasovsky [this message]
2026-09-29 9:24 ` [PATCH proxmox-backup 0/2] fix #7606: verify: s3: handle transient fetch errors and add retry Christian Ebner
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=20260929091439.579314-1-git@krasovs.ky \
--to=git@krasovs.ky \
--cc=c.ebner@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