We are also seeing this. We're now stuck on old kernels until this is
fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2050098
Title:
cgroup2 broken since 5.15.0-90-generic?
I'm concerned with the security implications of being frozen on a kernel
we can't update. I suspect we should start testing an HWE kernel. That
raises other issues, since there are lots of other features we also need
to work, so it's going to require a fair amount of testing. I'd
accelerate our mov
In src/plugins/cgroup/v2/ebpf.c, comment out logging. I.e. change
attr.log_level = 1;
attr.log_buf = (size_t) log;
attr.log_size = sizeof(log);
to
attr.log_level =
>From timing I suspect kernel.org
2dcb31e65d26a29a6842500e904907180e80a091, but I don't understand the
code so I can't tell whether there's actually a problem there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
h
However the same patch is in 6.5. I give up. At least I have a
workaround.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2050098
Title:
cgroup2 broken since 5.15.0-90-generic?
S
Furthermore, slurm doesn't actually use the log data that the kernel
would pass back. So my code is better even with kernels that work. Why
pass a log buffer that you aren't going to use?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
For what it's worth, we've been running a file server for several weeks
with the 2.1.14 .ko files in 22.04 with no problem. I didn't try to
cherry pick the one fix as I'd prefer to have the whole 2.1.14.
--
You received this bug notification because you are a member of Kernel
Packages, which is s
This issue is different. It's another problem with block copy. But
that's known to still be an issue. It's why block copy is disabled in
2.2.1. This is only an issue for the Jammy HWE, which has 2.2.0. No one
should be shipping 2.2.0 with anything. It should be replaced with 2.2.1
at least.
--
Yo
Actually, it may not be an issue even for Jammy HWE. My copy shows block
cloning as an option that's off.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data
it's likely to take a while. It's been committed but not released. They
chose to cherry pick the patch, so the version will still show as 2.1.5.
A lot of us would prefer going to 2.1.14, but there are enough other
changes that Ubuntu staff didn't want to do it. I'm considering building
my own zfs m
Since I was just referenced, note that I wouldn't favor putting 2.2 into
Jammy. I would, however, prefer to see the latest 2.1.x.
2.2 is still seeing a substantial number of bug fixes. It will probably
be ok by the release date of 24.04, but I still wouldn't change major
versions for Jammy.
--
Y
Public bug reported:
I just upgraded an NFS server from 20.04 to 22.04. Because of problems
in my setup, it didn't come up cleanly. As part of recovery I did
"systemctl restart nfs-server." I did this after two reboots. In both
cases shortly thereafter I got one or more backtraces in syslog
Aug 1
I've also seen this. I wondered if the problem is that the libraries and
utilities haven't been updated. I doubt that it's intended for a version
0.8.3 ZFS send and receive to run on a ZFS 2.0.2. kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Note that there are serious bugs with ZFS encryption. Most involve send
| receive, but not all. I strongly recommend against using it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/199
14 matches
Mail list logo
