public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: Robert Obkircher <r.obkircher@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup 01/10] task tracking: count Reclaim datastore operations as writes
Date: Tue, 5 May 2026 15:48:52 +0200	[thread overview]
Message-ID: <ae053c1f-ee37-414a-ae36-622879fd599a@proxmox.com> (raw)
In-Reply-To: <20260430150607.330413-5-r.obkircher@proxmox.com>

one question regarding the accounting

On 4/30/26 5:04 PM, Robert Obkircher wrote:
> This ensures that changing a Write to a Reclaim does not break forward
> compatibility when older versions read the counters.
> 
> Ideally, Write operations would also be tracked separately to display
> them as conflicts of the GarbageCollection maintenance mode, but an
> extra field would lead to parse errors in older versions which are not
> always propagated (for example when cloning a Datastore) and would
> thus result in incorrect values.

The following test works without issues:

#[test]
fn test_active_operation_parsing() {
     let raw_str = 
"[{\"pid\":111,\"starttime\":111,\"active_operations\":{\"read\":1,\"write\":3,\"reclaim\":2}}]";
     assert!(serde_json::from_str::<Vec<TaskOperations>>(&raw_str).is_ok());
}

So reclaim operations could be accounted for by writes and an optional 
reclaim for the time being (ignored and not written by older versions), 
allowing to switch in the future, once all versions are expected to 
handle it directly. Or am I missing something here?

> 
> Signed-off-by: Robert Obkircher <r.obkircher@proxmox.com>
> ---
>   pbs-datastore/src/task_tracking.rs | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/pbs-datastore/src/task_tracking.rs b/pbs-datastore/src/task_tracking.rs
> index 44a4522dc..c8833759b 100644
> --- a/pbs-datastore/src/task_tracking.rs
> +++ b/pbs-datastore/src/task_tracking.rs
> @@ -106,6 +106,7 @@ pub fn update_active_operations(
>       let mut updated_active_operations = match operation {
>           Operation::Read => ActiveOperationStats { read: 1, write: 0 },
>           Operation::Write => ActiveOperationStats { read: 0, write: 1 },
> +        Operation::Reclaim => ActiveOperationStats { read: 0, write: 1 },
>           Operation::Lookup => ActiveOperationStats { read: 0, write: 0 },
>       };
>       let mut found_entry = false;
> @@ -121,6 +122,7 @@ pub fn update_active_operations(
>                               match operation {
>                                   Operation::Read => task.active_operations.read += count,
>                                   Operation::Write => task.active_operations.write += count,
> +                                Operation::Reclaim => task.active_operations.write += count,
>                                   Operation::Lookup => (), // no IO must happen there
>                               };
>                               updated_active_operations = task.active_operations;





  reply	other threads:[~2026-05-05 13:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 15:05 [RFC proxmox{,-backup} 00/13] gc maintenance mode and full datastore protection Robert Obkircher
2026-04-30 15:05 ` [PATCH proxmox 1/3] pbs-api-types: add datastore operation variant for reclaiming storage Robert Obkircher
2026-04-30 15:05 ` [PATCH proxmox 2/3] pbs-abi-types: add GarbageCollection maintenance mode Robert Obkircher
2026-05-05 13:48   ` Christian Ebner
2026-04-30 15:05 ` [PATCH proxmox 3/3] pbs-api-types: add reserved space to datastore tuning options Robert Obkircher
2026-04-30 15:05 ` [PATCH proxmox-backup 01/10] task tracking: count Reclaim datastore operations as writes Robert Obkircher
2026-05-05 13:48   ` Christian Ebner [this message]
2026-04-30 15:05 ` [PATCH proxmox-backup 02/10] datastore: open datastores with Reclaim instead of Write operation Robert Obkircher
2026-05-05 13:49   ` Christian Ebner
2026-04-30 15:05 ` [PATCH proxmox-backup 03/10] fix #5797: www: display new GarbageCollection maintenance mode Robert Obkircher
2026-05-05 13:49   ` Christian Ebner
2026-04-30 15:05 ` [PATCH proxmox-backup 04/10] www: access active operation fields by name instead of index Robert Obkircher
2026-04-30 15:05 ` [PATCH proxmox-backup 05/10] www: don't claim that all active writers are gc mode conflicts Robert Obkircher
2026-04-30 15:05 ` [PATCH proxmox-backup 06/10] chunk_store: add method to limit file system usage Robert Obkircher
2026-04-30 15:05 ` [PATCH proxmox-backup 07/10] chunk_store: check file system space before inserting new chunks Robert Obkircher
2026-04-30 15:05 ` [PATCH proxmox-backup 08/10] datastore: check file system space for blobs and group notes Robert Obkircher
2026-04-30 15:05 ` [PATCH proxmox-backup 09/10] api2: backup: check space for fixed and dynamic index files Robert Obkircher
2026-04-30 15:05 ` [PATCH proxmox-backup 10/10] fix #7254: datastore: refuse new backps when capacity is almost full Robert Obkircher
2026-05-05 13:48   ` Christian Ebner
2026-05-05 13:49   ` Christian Ebner
2026-05-05 14:06 ` [RFC proxmox{,-backup} 00/13] gc maintenance mode and full datastore protection 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=ae053c1f-ee37-414a-ae36-622879fd599a@proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=r.obkircher@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