all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>,
	pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] [PATCH proxmox-backup 1/3] GC: refactor chunk removal helper
Date: Wed, 15 Oct 2025 11:10:26 +0200	[thread overview]
Message-ID: <7b909266-0597-422a-aed7-7dcc91e6bb8a@proxmox.com> (raw)
In-Reply-To: <20251015083840.569025-2-f.gruenbichler@proxmox.com>

one comment inline

On 10/15/25 10:38 AM, Fabian Grünbichler wrote:
> simplify the callback, and move the error handling to the helper..
> 
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
>   pbs-datastore/src/chunk_store.rs | 27 ++++++++++++---------------
>   pbs-datastore/src/datastore.rs   |  2 +-
>   2 files changed, 13 insertions(+), 16 deletions(-)
> 
> diff --git a/pbs-datastore/src/chunk_store.rs b/pbs-datastore/src/chunk_store.rs
> index 6e50327cb..1c7df9074 100644
> --- a/pbs-datastore/src/chunk_store.rs
> +++ b/pbs-datastore/src/chunk_store.rs
> @@ -415,19 +415,13 @@ impl ChunkStore {
>                       stat.st_size as u64,
>                       bad,
>                       status,
> -                    |status| {
> -                        if let Err(err) =
> -                            unlinkat(Some(dirfd), filename, UnlinkatFlags::NoRemoveDir)
> -                        {
> -                            if bad {
> -                                status.still_bad += 1;
> -                            }
> -                            bail!(
> +                    || {
> +                        unlinkat(Some(dirfd), filename, UnlinkatFlags::NoRemoveDir).map_err(|err| {
> +                            format_err!(
>                                   "unlinking chunk {filename:?} failed on store '{}' - {err}",
>                                   self.name,
> -                            );
> -                        }
> -                        Ok(())
> +                            )
> +                        })
>                       },
>                   )?;
>               }
> @@ -441,9 +435,7 @@ impl ChunkStore {
>       /// status accordingly.
>       ///
>       /// If the chunk should be removed, the [`remove_callback`] is executed.
> -    pub(super) fn check_atime_and_update_gc_status<
> -        T: FnOnce(&mut GarbageCollectionStatus) -> Result<(), Error>,
> -    >(
> +    pub(super) fn check_atime_and_update_gc_status<T: FnOnce() -> Result<(), Error>>(
>           atime: i64,
>           min_atime: i64,
>           oldest_writer: i64,
> @@ -453,7 +445,12 @@ impl ChunkStore {
>           remove_callback: T,
>       ) -> Result<(), Error> {
>           if atime < min_atime {
> -            remove_callback(gc_status)?;
> +            if let Err(err) = remove_callback() {
> +                if bad {
> +                    gc_status.still_bad += 1;
> +                    return Err(err);

Unless I'm overseeing something, this will now no longer propagate the 
error in case the removal of a non-bad chunk fails? Previously the error 
was returned independent from the `bad` state.

> +                }
> +            }
>               if bad {
>                   gc_status.removed_bad += 1;
>               } else {
> diff --git a/pbs-datastore/src/datastore.rs b/pbs-datastore/src/datastore.rs
> index a6b17e3c3..21998a157 100644
> --- a/pbs-datastore/src/datastore.rs
> +++ b/pbs-datastore/src/datastore.rs
> @@ -1671,7 +1671,7 @@ impl DataStore {
>                           content.size,
>                           bad,
>                           &mut gc_status,
> -                        |_status| {
> +                        || {
>                               if let Some(cache) = self.cache() {
>                                   // ignore errors, phase 3 will retry cleanup anyways
>                                   let _ = unsafe { cache.remove(&digest) };



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

  reply	other threads:[~2025-10-15  9:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15  8:38 [pbs-devel] [PATCH proxmox-backup 0/3] GC refactor follow-ups Fabian Grünbichler
2025-10-15  8:38 ` [pbs-devel] [PATCH proxmox-backup 1/3] GC: refactor chunk removal helper Fabian Grünbichler
2025-10-15  9:10   ` Christian Ebner [this message]
2025-10-15  9:46     ` Fabian Grünbichler
2025-10-15  9:56       ` Christian Ebner
2025-10-15 10:04         ` Fabian Grünbichler
2025-10-15  8:38 ` [pbs-devel] [PATCH proxmox-backup 2/3] GC: rename helper to cond_sweep_chunk Fabian Grünbichler
2025-10-15  9:12   ` Christian Ebner
2025-10-15  8:38 ` [pbs-devel] [PATCH proxmox-backup 3/3] GC: mark cond_sweep_chunk helper as unafe Fabian Grünbichler
2025-10-15  9:13   ` Christian Ebner
2025-10-15 10:14 ` [pbs-devel] superseded: [PATCH proxmox-backup 0/3] GC refactor follow-ups 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=7b909266-0597-422a-aed7-7dcc91e6bb8a@proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=f.gruenbichler@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