From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id F0F89B8DDA for ; Wed, 6 Dec 2023 15:46:09 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CE7303D1E for ; Wed, 6 Dec 2023 15:46:09 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 6 Dec 2023 15:46:09 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 1A1A4426BB for ; Wed, 6 Dec 2023 15:46:09 +0100 (CET) Message-ID: <1efc8388-0c8f-4b34-9ba6-e0c8d52ab93c@proxmox.com> Date: Wed, 6 Dec 2023 15:46:08 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: Thomas Lamprecht , Proxmox Backup Server development discussion , =?UTF-8?Q?Fabian_Gr=C3=BCnbichler?= References: <20231206132834.240700-1-g.goller@proxmox.com> <1764237283.1899.1701870086441@webmail.proxmox.com> <658c5de3-d130-42d5-951c-9ccd58daa0fe@proxmox.com> From: Gabriel Goller In-Reply-To: <658c5de3-d130-42d5-951c-9ccd58daa0fe@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.155 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pbs-devel] [PATCH v2 proxmox{, -backup} 0/2] Move ProcessLocker to tmpfs X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2023 14:46:10 -0000 On 12/6/23 15:36, Thomas Lamprecht wrote: > Am 06/12/2023 um 14:41 schrieb Fabian Grünbichler: >> [..] > Wolfgang and I discussed this last week or so, and we'd use a flag living > in `/run/proxmox-backup` touched via proxmox-backup-server.postinst on > upgrade to signal that the new locking should not be used yet, after reboot > all old daemons are gone and so is the flag, so the new locking can be used. > > Manual downgrades we don't care for, as those need special attention anyway. > The duplicate code can then be ripped out in the next major release. > > Wolfgang has a PoC about this on his staff repo IIRC. We should also add a section in the upgrade guide on how to upgrade *without* rebooting, so stopping all old processes, removing the flag manually, updating, then starting the new process. (I'd guess a lot of people don't want to reboot)