This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the
** Changed in: zfs-linux (Ubuntu Lunar)
Status: Confirmed => Invalid
** Changed in: zfs-linux (Ubuntu Jammy)
Status: Confirmed => Invalid
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-aws/5.15.0-1034.38
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1036.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 6.2.0-18.18
---
linux (6.2.0-18.18) lunar; urgency=medium
* lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750)
* lunar/linux 6.2 fails to boot on arm64 (LP: #2011748)
- SAUCE: Revert "efi: random: fix NULL-deref when
This bug is awaiting verification that the linux-allwinner/5.19.0-1009.9
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-riscv/5.19.0-1015.16
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
@Matthew, that's a good question. Since you are using 22.04 with the
5.15 kernel, you'll need to wait for the 5.15.0-68.75 kernel to land in
-updates as it is still in -proposed ATM.
The zfs-linux user space tools, shouldn't need an update for this bug
but even if it did, the LXD snap bundles
Please, forgive the newbie question.
I had to manually install the 5.15-0-47-generic kernel on 22.04.2 LTS to
work around the ZFS shiftfs problem as it impacted production LXD
containers which relied upon local ZFS storage access within the
containers.
Does the kernel fix resolve the issue for
This bug is awaiting verification that the linux-starfive/5.19.0-1014.16
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
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/1990849
Title:
LXD containers using shiftfs on
This bug is awaiting verification that the linux-azure/5.19.0-1022.23
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1021.22
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/1990849
Title:
LXD containers using shiftfs on ZFS
This bug is awaiting verification that the linux/5.15.0-68.75 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change
This bug was fixed in the package linux - 5.19.0-35.36
---
linux (5.19.0-35.36) kinetic; urgency=medium
* kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)
* CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461
linux (5.19.0-34.35) kinetic;
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed => Fix Committed
--
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/1990849
Title:
LXD containers using shiftfs on ZFS or
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
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/1990849
Title:
LXD containers using shiftfs on
This bug is awaiting verification that the linux/5.19.0-35.36 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Lunar)
Status: Confirmed => Fix Committed
https://lists.ubuntu.com/archives/kernel-team/2023-January/136731.html
--
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/1990849
Title:
LXD containers using shiftfs on ZFS or TMPFS
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
** Also affects: zfs-linux (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux
https://lists.ubuntu.com/archives/kernel-team/2023-January/136719.html
--
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/1990849
Title:
LXD containers using shiftfs on ZFS or TMPFS
We are waiting for the maintainer's decision on that patch. I've done
everything from my side. I'm sorry that it takes too long to be landed
in the kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
I've tested the patch on kernel 5.15.0-57.63 and it solves the issue for
me.
Aleksandr - Andrea asked you in your kernel-team thread to rebase the
patch on master-next, hopefully if you can do this it'll be accepted.
Keen to see this issue fixed in jammy as it's breaking Docker+Sysbox
containers
Any updates?
--
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/1990849
Title:
LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
Status in linux package in Ubuntu:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu Kinetic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Kinetic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Kinetic)
** No longer affects: zfs-linux (Ubuntu Kinetic)
** Also affects: linux
The attachment "0001-UBUNTU-SAUCE-shiftfs-fix-permanent-EOVERFLOW-
inside-.patch" seems to be a patch. If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message
** Patch added:
"0001-UBUNTU-SAUCE-shiftfs-fix-permanent-EOVERFLOW-inside-.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+attachment/5631210/+files/0001-UBUNTU-SAUCE-shiftfs-fix-permanent-EOVERFLOW-inside-.patch
--
You received this bug notification because you are a
Draft patch is ready
https://lists.ubuntu.com/archives/kernel-team/2022-November/134883.html
--
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/1990849
Title:
LXD containers using
This degradation is not related to
SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency
change
--
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/1990849
Title:
LXD containers using
Dear friends,
Right now I'm on the way to understand what's happening with this.
# strace touch b
execve("/usr/bin/touch", ["touch", "b"], 0x7ffd29f848a8 /* 7 vars */) = 0
brk(NULL) = 0x56007dba6000
arch_prctl(0x3001 /* ARCH_??? */, 0x7fff436afcb0) = -1 EINVAL
Is there any plan or estimation on the fix?
--
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/1990849
Title:
LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
Status
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Anbox Cloud is affected by this too. We used shiftfs by default until
our 1.14 release in May 2022. According to the metrics we have there are
still a few users around with the 1.13 release which enables shiftfs on
ZFS.
--
You received this bug notification because you are a member of Kernel
This bug also breaks `lxc file push` functionality.
--
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/1990849
Title:
LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
(zfs-linux portion is to autopkgtest the reproducer, because this has
been pain multiple times now)
** Also affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux
I like the reproducer, i wonder if i should add it to zfs-linux as a
test case. Or maybe to the kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990849
Title:
LXD containers
Suspect is:
* refactoring of overlayfs fix to properly support shiftfs (LP: #1983640)
- SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Added sudo systemctl reload snap.lxd.daemon after disabling shiftfs.
** Description changed:
Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS
are broken.
Reproducer steps:
```
sudo snap install lxd
sudo snap set lxd shiftfs.enable=true
sudo lxd init
49 matches
Mail list logo
