From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <f.gruenbichler@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)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id CB03E9D6FC for <pve-user@lists.proxmox.com>; Fri, 24 Nov 2023 09:12:21 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B2DB8981C for <pve-user@lists.proxmox.com>; Fri, 24 Nov 2023 09:12:21 +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) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-user@lists.proxmox.com>; Fri, 24 Nov 2023 09:12:21 +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 E36D243A2E; Fri, 24 Nov 2023 09:12:20 +0100 (CET) Date: Fri, 24 Nov 2023 09:12:20 +0100 (CET) From: =?UTF-8?Q?Fabian_Gr=C3=BCnbichler?= <f.gruenbichler@proxmox.com> To: Proxmox VE user list <pve-user@lists.proxmox.com> Message-ID: <1624311989.1471.1700813540249@webmail.proxmox.com> In-Reply-To: <mailman.293.1700812718.422.pve-user@lists.proxmox.com> References: <6b9a818d-1256-435e-bce3-c3a8dbcd6671@proxmox.com> <969ADBB0-ACE4-4136-AAB5-DC02802A4CA8@volny.cz> <18793296-4C84-4345-B1D5-35E472D9278F@volny.cz> <mailman.293.1700812718.422.pve-user@lists.proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Normal X-Mailer: Open-Xchange Mailer v7.10.6-Rev54 X-Originating-Client: open-xchange-appsuite X-SPAM-LEVEL: Spam detection results: 0 AWL 0.065 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: [PVE-User] Proxmox VE 8.1 released! X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list <pve-user.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-user/> List-Post: <mailto:pve-user@lists.proxmox.com> List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Fri, 24 Nov 2023 08:12:21 -0000 > Daniel Plominski via pve-user <pve-user@lists.proxmox.com> hat am 24.11.2023 08:57 CET geschrieben: > > We are currently using: Proxmox 8.0.4 (Enterprise Sub) > > root@assg32:~# dpkg -l | grep zfs > ii libzfs4linux 2.1.12-pve1 amd64 OpenZFS filesystem library for Linux - general support > ii zfs-initramfs 2.1.12-pve1 all OpenZFS root filesystem capabilities for Linux - initramfs > ii zfs-zed 2.1.12-pve1 amd64 OpenZFS Event Daemon > ii zfsutils-linux 2.1.12-pve1 amd64 command-line tools to manage OpenZFS filesystems > root@assg32:~# > > Are we affected by any ZFS "Silent Corruption Bugs"? according to the upstream bug tracker, there is one (hard to trigger!) issue that probably dates back to 2013. > On 19.11.2023 we had unexplained ZFS errors on a node: > > root@assg26:~# zpool status -v > pool: rpool > state: ONLINE > status: One or more devices is currently being resilvered. The pool will > continue to function, possibly in a degraded state. > action: Wait for the resilver to complete. > scan: resilver in progress since Sun Nov 19 08:30:03 2023 > 309G scanned at 2.31G/s, 3.00M issued at 22.9K/s, 742G total > 0B resilvered, 0.00% done, no estimated completion time > config: > > NAME STATE READ WRITE CKSUM > rpool ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > spare-0 ONLINE 0 0 0 > nvme-eui.35354830526004030025384700000003-part3 ONLINE 0 0 3 > nvme0n1p3 ONLINE 0 0 0 > nvme-eui.35354830526003280025384700000003-part3 ONLINE 0 0 3 both your vdevs had 3 checksum errors - that sound peculiar, but more like a hardware issue (memory?). can you try scrubbing the pool when the resilvering is completed?