From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Maximiliano Sandoval R <m.sandoval@proxmox.com>
Subject: Re: [pbs-devel] [PATCH offline-mirror] mirror: Use PathBuf instead of strings for paths
Date: Sat, 25 Nov 2023 17:20:57 +0100 [thread overview]
Message-ID: <4c32001f-640b-4118-9d50-52a2305e1408@proxmox.com> (raw)
In-Reply-To: <20231121135031.171323-1-m.sandoval@proxmox.com>
Am 21/11/2023 um 14:50 schrieb Maximiliano Sandoval R:
> Joining the strings might results in a double `//` in a path. This was
> experienced in a ticket at our customer support in the following error:
>
> Error: unable to read
> "/var/lib/proxmox-offline-mirror/mirrors//.pool/sha256/<SOME_HASH>"
> - Input/output error (os error 5) after downloading ±60GB of data.
I mean, that's an example where one can view this slightly cosmetic issue,
not really the cause for the actual error, like your message tends to
suggest, I hope?!
next prev parent reply other threads:[~2023-11-25 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 13:50 Maximiliano Sandoval R
2023-11-25 16:20 ` Thomas Lamprecht [this message]
2023-11-27 8:37 ` Maximiliano Sandoval
2024-01-09 8:28 ` [pbs-devel] applied: " Fabian Grünbichler
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=4c32001f-640b-4118-9d50-52a2305e1408@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.sandoval@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.