public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH FOLLOW-UP proxmox-backup 2/4] task tracking: actually reset entry if desynced
Date: Thu, 20 Nov 2025 10:01:37 +0100	[thread overview]
Message-ID: <20251120090342.195791-1-f.gruenbichler@proxmox.com> (raw)
In-Reply-To: <20251120060245.21828-1-h.laimer@proxmox.com>

and warn about it. this *should* never happen unless the tracking file got
somehow messed with manually..

Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
This one fixes the replied-to patch to also correctly store an entry with no
tasks for the current PID, instead of just returning that there are none..

I am actually not sure how we should handle such a desync, we now pretend it's
the last task even though we don't know for sure.. maybe we should just error
out and let the Drop handler (not) handle it?

 pbs-datastore/src/task_tracking.rs | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/pbs-datastore/src/task_tracking.rs b/pbs-datastore/src/task_tracking.rs
index 10afebbe2..755d88fdf 100644
--- a/pbs-datastore/src/task_tracking.rs
+++ b/pbs-datastore/src/task_tracking.rs
@@ -94,7 +94,7 @@ pub fn get_active_operations_locked(
 pub fn update_active_operations(
     name: &str,
     operation: Operation,
-    count: i64,
+    mut count: i64,
 ) -> Result<ActiveOperationStats, Error> {
     let path = PathBuf::from(format!("{}/{}", crate::ACTIVE_OPERATIONS_DIR, name));
 
@@ -131,7 +131,15 @@ pub fn update_active_operations(
         None => Vec::new(),
     };
 
-    if !found_entry && count > 0 {
+    if !found_entry {
+        if count < 0 {
+            // if we don't have any operations at the moment, decrementing is not possible..
+            log::warn!(
+                "Active operations tracking mismatch - no current entry for {pid} but asked
+to decrement by {count}!"
+            );
+            count = 0;
+        };
         match operation {
             Operation::Read => updated_active_operations.read = count,
             Operation::Write => updated_active_operations.write = count,
-- 
2.47.3



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

  reply	other threads:[~2025-11-20  9:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20  6:02 [pbs-devel] [PATCH proxmox-backup v2] task tracking: improve pruning and fix accounting for missing entries Hannes Laimer
2025-11-20  9:01 ` Fabian Grünbichler [this message]
2025-11-20  9:01   ` [pbs-devel] [PATCH FOLLOW-UP proxmox-backup 3/4] task tracking: refactor code Fabian Grünbichler
2025-11-20  9:01   ` [pbs-devel] [RFC FOLLOW-UP proxmox-backup 4/4] task tracking: simplify public interface Fabian Grünbichler
2025-11-20  9:37   ` [pbs-devel] [PATCH FOLLOW-UP proxmox-backup 2/4] task tracking: actually reset entry if desynced Hannes Laimer
2025-11-20 10:22     ` 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=20251120090342.195791-1-f.gruenbichler@proxmox.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal