all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>, Fiona Ebner <f.ebner@proxmox.com>,
	Christian Ebner <c.ebner@proxmox.com>
Subject: Re: [pbs-devel] [PATCH v4 proxmox-backup 0/5] handle reader client disconnects
Date: Wed, 9 Apr 2025 15:20:21 +0200	[thread overview]
Message-ID: <b3ec36ab-717a-4f9f-8a9e-4eb21e45455f@proxmox.com> (raw)
In-Reply-To: <842c3240-b5e1-409f-b536-df4f514f3192@proxmox.com>

Am 09.04.25 um 14:55 schrieb Fiona Ebner:
> Am 09.04.25 um 14:53 schrieb Fiona Ebner:
>> Am 08.04.25 um 14:58 schrieb Christian Ebner:
>>> Reported in the community forum:
>>> [0] https://forum.proxmox.com/threads/158306/
>>>
>>
>> While I wasn't able to reproduce the exact issue as reported in the
>> forum thread I was able to run into a slightly different one by issuing
>> the following two commands
>>
>> proxmox-backup-client backup --repository 10.10.100.180:bigone
>> ex.pxar:example
>> proxmox-backup-client backup --repository 10.10.100.180:bigone
>> ex.pxar:example --change-detection-mode metadata
>>
>> resulting in a backup reader task that had to read no chunks (and that
>> was the correct timing for me to trigger the race I guess):
>>
>>> 2025-04-09T14:36:21+02:00: starting new backup reader datastore 'bigone': "/mnt/datastore/bigone"
>>> 2025-04-09T14:36:21+02:00: protocol upgrade done
>>> 2025-04-09T14:36:21+02:00: TASK ERROR: connection error: connection reset: connection reset
> 
> Totally forgot to mention that this issue was gone with both patched
> client and patched server :)

As in T-b? :-)


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


  reply	other threads:[~2025-04-09 13:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 12:58 Christian Ebner
2025-04-08 12:58 ` [pbs-devel] [PATCH v4 proxmox-backup 1/5] client: reader: drop dead code Christian Ebner
2025-04-08 12:58 ` [pbs-devel] [PATCH v4 proxmox-backup 2/5] backup debug: diff: refactor backup reader creation Christian Ebner
2025-04-08 12:58 ` [pbs-devel] [PATCH v4 proxmox-backup 3/5] api: reader: handle reader client disconnects Christian Ebner
2025-04-08 12:58 ` [pbs-devel] [PATCH v4 proxmox-backup 4/5] client: reader: add finish method to signal client state to server Christian Ebner
2025-04-09 13:53   ` Max Carrara
2025-04-09 14:27     ` Christian Ebner
2025-04-08 12:58 ` [pbs-devel] [PATCH v4 proxmox-backup 5/5] client: backup reader: call finish before dropping backup readers Christian Ebner
2025-04-09 12:53 ` [pbs-devel] [PATCH v4 proxmox-backup 0/5] handle reader client disconnects Fiona Ebner
2025-04-09 12:55   ` Fiona Ebner
2025-04-09 13:20     ` Thomas Lamprecht [this message]
2025-04-09 13:35       ` Fiona Ebner
2025-04-09 13:25   ` 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=b3ec36ab-717a-4f9f-8a9e-4eb21e45455f@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=c.ebner@proxmox.com \
    --cc=f.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 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