From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-devel-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 47A361FF15F for <inbox@lore.proxmox.com>; Mon, 7 Oct 2024 09:18:32 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7B24338913; Mon, 7 Oct 2024 09:18:55 +0200 (CEST) Date: Mon, 7 Oct 2024 09:12:46 +0200 (CEST) To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> In-Reply-To: <622071471.2095.1728054796983@webmail.proxmox.com> References: <mailman.189.1728050121.332.pve-devel@lists.proxmox.com> <622071471.2095.1728054796983@webmail.proxmox.com> MIME-Version: 1.0 Message-ID: <mailman.197.1728285534.332.pve-devel@lists.proxmox.com> List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Post: <mailto:pve-devel@lists.proxmox.com> From: Daniel Berteaud via pve-devel <pve-devel@lists.proxmox.com> Precedence: list Cc: Daniel Berteaud <dani@lapiole.org> X-Mailman-Version: 2.1.29 X-BeenThere: pve-devel@lists.proxmox.com List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> Subject: Re: [pve-devel] Proposal: support for atomic snapshot of all VM disks at once Content-Type: multipart/mixed; boundary="===============1954288502212496257==" Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com> --===============1954288502212496257== Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <dani@lapiole.org> X-Original-To: pve-devel@lists.proxmox.com Delivered-To: pve-devel@lists.proxmox.com 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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id A823BC2F32 for <pve-devel@lists.proxmox.com>; Mon, 7 Oct 2024 09:18:53 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8CF6938862 for <pve-devel@lists.proxmox.com>; Mon, 7 Oct 2024 09:18:53 +0200 (CEST) Received: from pmg.lapiole.org (pmg.lapiole.org [149.202.136.65]) (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 <pve-devel@lists.proxmox.com>; Mon, 7 Oct 2024 09:18:52 +0200 (CEST) Received: from pmg.lapiole.org (localhost [127.0.0.1]) by pmg.lapiole.org (Proxmox) with ESMTP id EDAA722B43 for <pve-devel@lists.proxmox.com>; Mon, 7 Oct 2024 09:12:48 +0200 (CEST) Received: from zmproxy.lapiole.org (zmproxy.lapiole.org [10.99.2.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pmg.lapiole.org (Proxmox) with ESMTPS for <pve-devel@lists.proxmox.com>; Mon, 7 Oct 2024 09:12:48 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zmproxy.lapiole.org (Postfix) with ESMTP id DC757125E16F; Mon, 7 Oct 2024 09:12:47 +0200 (CEST) Received: from zmproxy.lapiole.org ([127.0.0.1]) by localhost (zmproxy.lapiole.org [127.0.0.1]) (amavis, port 10026) with ESMTP id qE8PKrAW4fo9; Mon, 7 Oct 2024 09:12:47 +0200 (CEST) Received: from zmstore.lapiole.org (zmstore.lapiole.org [10.99.3.18]) by zmproxy.lapiole.org (Postfix) with ESMTP id 50E84125E16E for <pve-devel@lists.proxmox.com>; Mon, 7 Oct 2024 09:12:47 +0200 (CEST) Date: Mon, 7 Oct 2024 09:12:46 +0200 (CEST) From: Daniel Berteaud <dani@lapiole.org> To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Message-ID: <1324502869.237.1728285166262.JavaMail.zimbra@lapiole.org> In-Reply-To: <622071471.2095.1728054796983@webmail.proxmox.com> References: <mailman.189.1728050121.332.pve-devel@lists.proxmox.com> <622071471.2095.1728054796983@webmail.proxmox.com> Subject: Re: [pve-devel] Proposal: support for atomic snapshot of all VM disks at once MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailer: Zimbra 9.0.0_GA_20240905 (ZimbraWebClient - GC129 (Linux)/9.0.0_GA_20240905) Thread-Topic: Proposal: support for atomic snapshot of all VM disks at once Thread-Index: IifEcmgaMAegYY0BJ6aX46kDERp/2A== X-SPAM-LEVEL: Spam detection results: 0 AWL 0.016 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_PASS -0.1 DMARC pass policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record ----- Le 4 Oct 24, =C3=A0 17:13, Dietmar Maurer dietmar@proxmox.com a =C3= =A9crit : > We already make sure that shaphots of a group of volumes are atomic at qe= mu > level (VM is halted while snapshots are created), so I wonder > if there is any real advantage here? I think there could be one advantage : reduce the freez time during snapsho= t. I take regular snapshots of my VM, and it causes timeshifts of a few sec= onds (which chronyd inside the guest takes a bit a time to correct). It's j= ust a 1-4 sec, but it can cause issues. One example is minio, when used wit= h an OIDC login (as minio doesn't support any clock skew, login can fail if= minio lags just a few seconds behind the IDP) ++ --=20 Daniel Berteaud --===============1954288502212496257== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel --===============1954288502212496257==--