From: Cornelius Hoffmann <c.hoffmann@fu-berlin.de>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: pve-user@lists.proxmox.com, pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] [PVE-User] pbs - Nasty atime bug in Ubuntu's kernel-builtin zfs
Date: Wed, 16 Oct 2024 19:05:56 +0200 [thread overview]
Message-ID: <1669f329-e694-4a6f-9352-5c52b92050c2@fu-berlin.de> (raw)
In-Reply-To: <8fe24024-9416-45af-9d7a-d53dceee5543@proxmox.com>
Hi Thomas,
On 16.10.24 17:56, Thomas Lamprecht wrote:
> note that Proxmox maintains
> its own ZFS downstream package for both user-space tools and kernel
> module.
>
> Both the bad commit and the fix were in ZFS 2.2.3 [0], and unlike Ubuntu
> we never backported the problematic commit manually, so the Proxmox
> kernel and its ZFS module were never affected, FWICT.
Good to hear, mainly just wanted to make sure it stays that way :D
And maybe warn other people, since there are threads on the forum about
running PBS as a container, mostly LXC but also some that are not on
proxmox.
>
> I also tried the reproducer, as it is simple enough and just to be sure,
> and I could_not_ observe the broken behavior from ZFS.
I setup a PBS in a VM in the meantime for testing and also couldn't
reproduce it with your kernel.
Best,
Cornelius
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
WARNING: multiple messages have this Message-ID
From: Cornelius Hoffmann <c.hoffmann@fu-berlin.de>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: pve-user@lists.proxmox.com, pbs-devel@lists.proxmox.com
Subject: Re: [PVE-User] pbs - Nasty atime bug in Ubuntu's kernel-builtin zfs
Date: Wed, 16 Oct 2024 19:05:56 +0200 [thread overview]
Message-ID: <1669f329-e694-4a6f-9352-5c52b92050c2@fu-berlin.de> (raw)
In-Reply-To: <8fe24024-9416-45af-9d7a-d53dceee5543@proxmox.com>
Hi Thomas,
On 16.10.24 17:56, Thomas Lamprecht wrote:
> note that Proxmox maintains
> its own ZFS downstream package for both user-space tools and kernel
> module.
>
> Both the bad commit and the fix were in ZFS 2.2.3 [0], and unlike Ubuntu
> we never backported the problematic commit manually, so the Proxmox
> kernel and its ZFS module were never affected, FWICT.
Good to hear, mainly just wanted to make sure it stays that way :D
And maybe warn other people, since there are threads on the forum about
running PBS as a container, mostly LXC but also some that are not on
proxmox.
>
> I also tried the reproducer, as it is simple enough and just to be sure,
> and I could_not_ observe the broken behavior from ZFS.
I setup a PBS in a VM in the meantime for testing and also couldn't
reproduce it with your kernel.
Best,
Cornelius
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2024-10-23 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 15:06 [pbs-devel] " Cornelius Hoffmann
2024-10-16 15:06 ` [PVE-User] " Cornelius Hoffmann
2024-10-16 15:56 ` [pbs-devel] " Thomas Lamprecht
2024-10-16 15:56 ` Thomas Lamprecht
2024-10-16 17:05 ` Cornelius Hoffmann [this message]
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=1669f329-e694-4a6f-9352-5c52b92050c2@fu-berlin.de \
--to=c.hoffmann@fu-berlin.de \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-user@lists.proxmox.com \
--cc=t.lamprecht@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.