From: Cornelius Hoffmann <c.hoffmann@fu-berlin.de>
To: pbs-devel@lists.proxmox.com
Cc: pve-user@lists.proxmox.com
Subject: [pbs-devel] pbs - Nasty atime bug in Ubuntu's kernel-builtin zfs
Date: Wed, 16 Oct 2024 17:06:05 +0200 [thread overview]
Message-ID: <a65b8433-c6d0-4179-977a-be677f98441a@fu-berlin.de> (raw)
Hi,
I ran in to a very nasty bug with the zfs version included in Ubuntu
(NOT the pbs default kernel, I'm running PBS in a container), which is
the base for Proxmox as well as far as I understand it and wanted to
warn about a problem with access times that is encountered there.
Essentially, this is [1] and it causes the access time update of a
`touch` command to fail and set it to epoch 0, so Jan 1, 1970. This will
cause all chunks that should not be pruned to have an extremely old
atime and thus be pruned, causing a corruption of all backups.
I'm writing here to make sure there is not maybe a kernel update waiting
with these changes. The newest zfs-linux version in noble has the bug
fixed as it includes [2], but that change is only visible in the dkms
module, which I installed to fix this problem in the meantime.
Cc to the pve-user list, if anybody is also running pbs on the normal
Ubunutu noble kernel on zfs storage.
Best,
Cornelius
[1] https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2077487
[2] https://github.com/openzfs/zfs/pull/15773
--
Cornelius Hoffmann (he/him er/ihm)
#gernperDu
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2024-10-23 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 15:06 Cornelius Hoffmann [this message]
2024-10-16 15:56 ` [pbs-devel] [PVE-User] " Thomas Lamprecht
2024-10-16 17:05 ` Cornelius Hoffmann
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=a65b8433-c6d0-4179-977a-be677f98441a@fu-berlin.de \
--to=c.hoffmann@fu-berlin.de \
--cc=pbs-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox