public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Thomas Lamprecht" <t.lamprecht@proxmox.com>,
	"Proxmox Backup Server development discussion"
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] applied-series: [PATCH proxmox-backup v9 0/4] refactor datastore locking to use tmpfs
Date: Thu, 27 Mar 2025 11:02:35 +0100	[thread overview]
Message-ID: <D8QYNR728B9Y.TP3UY41PTSXC@proxmox.com> (raw)
In-Reply-To: <6ba0c8f7-1a61-4bb9-80c2-9fff4918ad75@proxmox.com>

On Wed Mar 26, 2025 at 4:36 PM CET, Thomas Lamprecht wrote:
> Am 26.03.25 um 12:44 schrieb Shannon Sterz:> The goal of this series is to make it safer to remove backup groups &
>> snapshots by separating the corresponding directories from their lock
>> files. By moving the lock files to the tmpfs-backed '/run' directory,
>> we also make sure that the lock files get cleaned up when the system
>> reboots.
>>
>> This series refactors the locking mechanism inside the `DataStore`,
>> `BackupDir` and `BackupGroup` traits. In a first step locking methods
>> are added and the existing code is refactored to use them. Commit two
>> derives a lock file name under '/run' for each group/snapshot. It also
>> adds double stat'ing. To avoid issues when upgrading, the file
>> `/run/proxmox-backup/old-locking` is created through a post-install
>> hook which is used to determine whether the system has been rebooted
>> and we can safely use the new locking mechanism.
>>
>> The third commit refactors locking for manifests and brings it in-line
>> with the group/snapshot locks. Finally, the last commit fixes a race
>> condition when changing the owner of a datastore.
>
>> Shannon Sterz (4):
>>   datastore/api/backup: prepare for fix of #3935 by adding lock helpers
>>   fix #3935: datastore/api/backup: move datastore locking to '/run'
>>   fix #3935: datastore: move manifest locking to new locking method
>>   fix: api: avoid race condition in set_backup_owner
>>
>
> applied series, added Wolfgang's Acked-by – feel encouraged to pick such
> things up already for a new revision, especially an A-b is less problematic
> with minor changes as long as the overall design stays the same – and also
> fixed a minor compile warning about an unused import that stemmed from
> intra-revision changes, thanks!

thanks a bunch! should i always add all trailers mentioned on list?
wasn't sure about the `Acked-by` tbh ^^'


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

  reply	other threads:[~2025-03-27 10:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 11:44 [pbs-devel] " Shannon Sterz
2025-03-26 11:44 ` [pbs-devel] [PATCH proxmox-backup v9 1/4] datastore/api/backup: prepare for fix of #3935 by adding lock helpers Shannon Sterz
2025-03-26 11:44 ` [pbs-devel] [PATCH proxmox-backup v9 2/4] fix #3935: datastore/api/backup: move datastore locking to '/run' Shannon Sterz
2025-03-26 15:14   ` Thomas Lamprecht
2025-03-26 15:22   ` Thomas Lamprecht
2025-03-26 11:44 ` [pbs-devel] [PATCH proxmox-backup v9 3/4] fix #3935: datastore: move manifest locking to new locking method Shannon Sterz
2025-03-26 11:44 ` [pbs-devel] [PATCH proxmox-backup v9 4/4] fix: api: avoid race condition in set_backup_owner Shannon Sterz
2025-03-26 15:36 ` [pbs-devel] applied-series: [PATCH proxmox-backup v9 0/4] refactor datastore locking to use tmpfs Thomas Lamprecht
2025-03-27 10:02   ` Shannon Sterz [this message]
2025-03-28  7:51     ` Wolfgang Bumiller
2025-03-28  8:17       ` Shannon Sterz

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=D8QYNR728B9Y.TP3UY41PTSXC@proxmox.com \
    --to=s.sterz@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=t.lamprecht@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