[pbs-devel] applied-series: [PATCH proxmox-backup v3 0/7] wait for active operations to finish before s3 refresh

[Fabian Grünbichler]

On Thu, 13 Nov 2025 15:22:07 +0100, Christian Ebner wrote:
> Datastore contents located on the s3 backend can be refreshed on the local
> datastore cache by running an s3-refresh, which will set the maintenance mode
> s3-refresh to block any read/write operation and fetch the contents to a
> temporary directory before moving them in place if the fetching was successful.
> 
> Setting the maintenance mode has however no effect on already active operations,
> which can cause inconsistencies once the s3 refresh moves the temporary folders
> in place.
> 
> [...]

Applied, thanks!

[1/7] api: admin: drop useless option for do_unmount_device() parameter
      commit: 30476ce11b702958eb7a7b668d1d135adfe4b6fb
[2/7] api: admin: rework waiting on active operations and maintenance locking
      commit: 8bf3d560768177450a299928dae30af986a48992
[3/7] api: admin: make s3 refresh handler sync
      commit: 524cf1e7bf0918a6bb916c4eeffdd6cc686f7701
[4/7] datastore: s3 refresh: set/unset maintenance mode in api handler
      commit: b98b22b2a6526fcf3217bc11a8b9fcbd0a883840
[5/7] api: datastore: wait for active operations to clear before s3 refresh
      commit: 29f4f48d92751f11410cd525323c2e0a436b40cf
[6/7] api: config: avoid unneeded backend instance on s3 store recreation
      commit: f5b2c6b86e7791104df62e384351490831e68b3c
[7/7] api: config: guard s3-refresh on datastore recreation
      commit: 7f36096e3b66f100ff59310663275f37c64cab8a

Best regards,
-- 
Fabian Grünbichler <f.gruenbichler at proxmox.com>