From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>, Stefan Sterz <s.sterz@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup] fix #4357: datastore: take into account namespaces when marking chunks
Date: Wed, 17 May 2023 11:35:53 +0200 [thread overview]
Message-ID: <94b5ca78-fe71-a4db-7da4-62ddd0908488@proxmox.com> (raw)
In-Reply-To: <20230420080853.119570-1-s.sterz@proxmox.com>
Am 20/04/2023 um 10:08 schrieb Stefan Sterz:
> previously when marking used chunks the namespace wasn't taken into
> account and valid snapshots were marked as "strange paths". this lead
> to a line in the log of a gc job such as this:
>
> found (and marked) 2 index files outside of expected directory scheme
>
> which some users perceived as an error. parse the namespace too and
> only mark the path as strange if parsing the namespace and/or backup
> dir fails.
>
> Signed-off-by: Stefan Sterz <s.sterz@proxmox.com>
> ---
> pbs-datastore/src/datastore.rs | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
applied, thanks!
prev parent reply other threads:[~2023-05-17 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 8:08 [pbs-devel] " Stefan Sterz
2023-05-17 9:35 ` Thomas Lamprecht [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=94b5ca78-fe71-a4db-7da4-62ddd0908488@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=s.sterz@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