From: Quenten <quenten+pve@cringe.zip>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] OpenZFS silent corruption bug
Date: Sat, 25 Nov 2023 11:04:23 +0000 [thread overview]
Message-ID: <010b018c0626eb09-926dde36-25a0-4143-9fce-2fad62b12982-000000@eu-west-2.amazonses.com> (raw)
Hi everyone,
This is my first time posting to the list, indeed the first time I
subscribe to it too. My reason for joining and posting is a recent
OpenZFS bug that appears to corrupt data:
https://github.com/openzfs/zfs/issues/15526.
I am not an expert on any of this, but I would just like to achieve two
things by posting here.
1. I want people to be aware of this bug, as everyone in the Github
issue seems to be on high alert
2. I want to know if Proxmox versions of OpenZFS are affected as well.
Does anyone on this list know more about this bug than me, in a more
technical sense? Are we affected? I personally checked on my Proxmox
install and "zfs version" returns "zfs-2.1.11-pve1". What is the best
course of action to take here?
----
Kind regards,
Quenten <quenten@cringe.zip>
next reply other threads:[~2023-11-25 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 11:04 Quenten [this message]
2023-11-25 11:30 ` netravnen+proxmoxlist
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=010b018c0626eb09-926dde36-25a0-4143-9fce-2fad62b12982-000000@eu-west-2.amazonses.com \
--to=quenten+pve@cringe.zip \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox