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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id E5F25B4372 for ; Fri, 1 Dec 2023 17:39:16 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C8E281A9B9 for ; Fri, 1 Dec 2023 17:39:16 +0100 (CET) Received: from mail-qv1-xf33.google.com (mail-qv1-xf33.google.com [IPv6:2607:f8b0:4864:20::f33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Fri, 1 Dec 2023 17:39:15 +0100 (CET) Received: by mail-qv1-xf33.google.com with SMTP id 6a1803df08f44-67a47104064so12770126d6.0 for ; Fri, 01 Dec 2023 08:39:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridscale-io.20230601.gappssmtp.com; s=20230601; t=1701448748; x=1702053548; darn=lists.proxmox.com; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=AAh7N6M5eRKriQScnY2xy3aYYHjf/ySWWguicj0OeXg=; b=TLlg1oiDLLqlCRaVekn8LVDEa+RoeXpnOsllrHxl0jGBLcKSXYHhUJwpgaA7uwysxl uxne8pwtlAZ9VmB+Uy6CctoaYwCJHVozMmUnELdYFRc2z72wZM0Q2+78MP4eD1w45KvB tv57ZleDb9+2/NaJXnHNKLh04pQ8s9wtglHhdgbGrd6geMc2Cve3b4qUycCKomhwa+QB WNs4sdtAYwVwClf0dLo8tUxpvOQsaUl9DL3pY6xZedOQdVC5hNjhgeaEbRQm5JNNhbA1 s2LAM3tONu1qEw3ggOlD2Dranjo15vjJ4R1qjTkVGZ404wSWatKAi1ORI/AOsLBfpr5G b3ow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701448748; x=1702053548; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=AAh7N6M5eRKriQScnY2xy3aYYHjf/ySWWguicj0OeXg=; b=Jo0xoX8U+2BBbmW9AceKEWLqEI3FvFHyQR/DEW6aB6rPY23ljc39v9DABGGdAxyNEK pMGYA52tvKqNlswHjeNMJcIyVzmlVkEmnA5mvO6PKY4lSCMxEELbccYkW8e+plfTIltt OhSow5kFtRorq6qKKuXrMcQ6OacAByO2rYHD+mrXUGPqKShbzqi9eMtRrTYTCMft50lf JYSr8MdF5+WJnVjemupTkTawN4fgme0exj41eHalYz59Kl392Z79UCslxp29rV9NnjpE ntq5SLKtRAwPXSNmub1rnXBXT36rS8niauC8rAszqnOb98gioAPi39Th4TZ24pgaSC44 NS5Q== X-Gm-Message-State: AOJu0Yxg7892PC2iSwDpfsefmd/6Iwk+nCmJTS62toaRI5pz8XQalmpN dgnmaQtUrt6nRNANzEr8+I4jRusUKMy+/1Alyq+FEQtRltjYLATxyUDADA== X-Google-Smtp-Source: AGHT+IHdm2UgE3PGX1LvgLyr6jVyRgvNlrb9OYfLgRn2M9ODZCIBlJ5Ge7YFJ4OkRMgC58tdxxZG7L4URqw1bN27amU= X-Received: by 2002:a0c:c487:0:b0:67a:542a:d91d with SMTP id u7-20020a0cc487000000b0067a542ad91dmr14902884qvi.2.1701448747926; Fri, 01 Dec 2023 08:39:07 -0800 (PST) MIME-Version: 1.0 From: Benjamin Hofer Date: Fri, 1 Dec 2023 17:38:58 +0100 Message-ID: To: pve-user@lists.proxmox.com X-SPAM-LEVEL: Spam detection results: 0 AWL 1.008 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DMARC_PASS -0.1 DMARC pass policy HTML_MESSAGE 0.001 HTML included in message RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust 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 - Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: [PVE-User] Backup server: Backup not finished because of network outage, can failing backup potentially cause read-only root FS? X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2023 16:39:16 -0000 Dear Proxmox community, we had a 13 minutes firewall outage. During that time, there was an hourly VM backup running. The backup didn't finish as the Proxmox VE node couldn't reach the backup server. I see the "GET" API request (return code 101) that starts the backup in the PBS API logs. The HTTP "PUT" to transfer the backup is missing. Unfortunately the backup's task log is missing. It obviously got rotated. During that time, the root filesystem of the VM changed to read-only. To find out if things are related or not, it'll be helpful for me to answer the following questions: 1) What happens when a Proxmox backup is started and PBS is not reachable anymore to transfer the backup? 2) In general, is there a (small) chance of a (failing) VM backup causing the filesystem to be read-only afterwards? I read that qemu-guest-agent calls fsfreeze during Proxmox VM backup. What are the impacts of fsfreeze? How are errors handled? Are there other potential risks? Here's the VM config: agent: 1 bios: seabios boot: cdn bootdisk: scsi0 cipassword: ********** ciuser: cloudadmin cores: 8 cpu: Skylake-Server-noTSX-IBRS description: VM Description hotplug: network,disk,usb kvm: 1 machine: q35 memory: 32768 name: vm-name net0: virtio=26:4B:29:B1:71:89,bridge=vmbr0,tag=37 numa: 0 onboot: 0 ostype: l26 protection: 1 rng0: source=/dev/urandom scsi0: ceph:vm-108-disk-0,size=255180M,ssd=1 scsihw: virtio-scsi-single serial0: socket smbios1: uuid=e8736d61-9a25-4f89-9f6d-a84ef25c42cc sockets: 1 tablet: 1 vga: qxl vmgenid: 9d3233e9-6bc1-43e8-be50-39597b6a5034 I highly appreciate any answers and thoughts! All the best Benjamin