From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Proxmox VE 8.1 released!
Date: Fri, 24 Nov 2023 09:12:20 +0100 (CET) [thread overview]
Message-ID: <1624311989.1471.1700813540249@webmail.proxmox.com> (raw)
In-Reply-To: <mailman.293.1700812718.422.pve-user@lists.proxmox.com>
> 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?
next prev parent reply other threads:[~2023-11-24 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 14:27 [pve-devel] " Martin Maurer
2023-11-23 14:27 ` [PVE-User] " Martin Maurer
2023-11-23 22:35 ` Jan Vlach
2023-11-23 22:43 ` Jan Vlach
[not found] ` <mailman.293.1700812718.422.pve-user@lists.proxmox.com>
2023-11-24 8:12 ` Fabian Grünbichler [this message]
[not found] ` <mailman.296.1700814059.422.pve-user@lists.proxmox.com>
2023-11-24 8:32 ` Fabian Grünbichler
2023-11-24 14:24 ` Jan Vlach
2023-11-24 7:27 ` [pve-devel] " Fabian Grünbichler
2023-11-24 7:27 ` Fabian Grünbichler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1624311989.1471.1700813540249@webmail.proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.