Thomas Lamprecht e22ad28302 GC scheduling: avoid triggering operation tracking error for upfront checks ...

without that one gets a "failed to lookup datastore X" in the log for
every datastore that is in read-only or offline maintenance mode,
even if they aren't scheduled for GC anyway.

Avoid that by first opening the datastore through a Lookup operation,
and only re-open it as Write op once we know that GC needs to get
scheduled for it.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

2022-05-12 11:36:56 +02:00

..

proxmox_backup_debug

rust fmt for pbs src

2022-04-14 14:03:46 +02:00

proxmox_backup_manager

sync/pull: make namespace aware

2022-05-12 09:33:50 +02:00

proxmox_tape

cli: tape key-restore: print more info for better ux

2022-04-13 16:59:47 +02:00

docgen.rs

rust fmt for pbs src

2022-04-14 14:03:46 +02:00

proxmox-backup-api.rs

rust fmt for pbs src

2022-04-14 14:03:46 +02:00

proxmox-backup-debug.rs

rust fmt for pbs src

2022-04-14 14:03:46 +02:00

proxmox-backup-manager.rs

sync/pull: make namespace aware

2022-05-12 09:33:50 +02:00

proxmox-backup-proxy.rs

GC scheduling: avoid triggering operation tracking error for upfront checks

2022-05-12 11:36:56 +02:00

proxmox-daily-update.rs

bin: daily-update: use syslog/log crates instead of printing to stderr

2022-02-22 10:58:44 +01:00

proxmox-tape.rs

api-types: introduce BackupType enum and Group/Dir api types

2022-04-15 13:12:46 +02:00

sg-tape-cmd.rs

rust fmt for pbs src

2022-04-14 14:03:46 +02:00