[PVE-User] Proxmox VE 8.1 released!

[Fabian Grünbichler]

> Daniel Plominski via pve-user <pve-user at lists.proxmox.com> hat am 24.11.2023 08:57 CET geschrieben:
>
> We are currently using: Proxmox 8.0.4 (Enterprise Sub)
> 
> root at 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 at 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 at 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?