[Kernel-packages] [Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
The bugfix has been working as expected over the past 3 days on my 2 systems: Intel NUC (kernel 5.11.0-37-generic) GCP Instance (kernel 5.11.0-1020-gcp) None of my syncoid jobs have failed, I am no longer using the --no- resume (-s) flag as a workaround. -- 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/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Committed Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
While hot-fixing the issue is fine, I feel like this won't be the last bug like this we run into as long as we choose to mix-and-match versions. Wouldn't the better solution be adding HWE ZFS userland packages to match the kernel module? -- 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/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Committed Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872510] Re: Slow / Broken Boot on Battery Power
This was an issue of support from the linux-firwmare package, my hardware was not supported in earlier versions. I've installed the linux-firwmare avaiable in 21.04 (1.191), and it fixed all of my hardware issues. -- 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/1872510 Title: Slow / Broken Boot on Battery Power Status in linux package in Ubuntu: Confirmed Bug description: The behavior is the same booting from USB to install the OS, and booting from NVMe on an installed OS. I'm using disk encryption, but I don't believe it plays a factor. When I boot plugged in to power, the system behaves normally, even once battery is disconnected. I can put the system to sleep on battery, wake on battery, and everything is fine. The initial boot on battery just does not seem happy either way. I've tried both with and without TLP installed. This behavior was present on 18.04, but I assumed it was an "old kernel" issue as this is fairly new hardware. I was previously on Manjaro w/ kernel 5.4, and the system was fine, but using Focal Fossa on kernel 5.4 presents the boot issue. It appears to get through most of the boot process but I don't ever see the login screen, it sits hung at a black screen and a mouse. Overall the boot process itself feels very sluggish. Please let me know if there's more information I can provide - thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lyndon 1871 F pulseaudio /dev/snd/controlC0: lyndon 1871 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 11:18:18 2020 InstallationDate: Installed on 2020-04-03 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5585 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.4 dmi.board.name: 0N999T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 2.4.4 dmi.modalias: dmi:bvnDellInc.:bvr2.4.4:bd11/12/2019:svnDellInc.:pnInspiron5585:pvr2.4.4:rvnDellInc.:rn0N999T:rvrA00:cvnDellInc.:ct10:cvr2.4.4: dmi.product.family: Inspiron dmi.product.name: Inspiron 5585 dmi.product.sku: 092B dmi.product.version: 2.4.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872510] Re: Slow / Broken Boot on Battery Power
I've worked around whatever bug by forcing iommu to soft ~$ grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash iommu=soft" -- 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/1872510 Title: Slow / Broken Boot on Battery Power Status in linux package in Ubuntu: Confirmed Bug description: The behavior is the same booting from USB to install the OS, and booting from NVMe on an installed OS. I'm using disk encryption, but I don't believe it plays a factor. When I boot plugged in to power, the system behaves normally, even once battery is disconnected. I can put the system to sleep on battery, wake on battery, and everything is fine. The initial boot on battery just does not seem happy either way. I've tried both with and without TLP installed. This behavior was present on 18.04, but I assumed it was an "old kernel" issue as this is fairly new hardware. I was previously on Manjaro w/ kernel 5.4, and the system was fine, but using Focal Fossa on kernel 5.4 presents the boot issue. It appears to get through most of the boot process but I don't ever see the login screen, it sits hung at a black screen and a mouse. Overall the boot process itself feels very sluggish. Please let me know if there's more information I can provide - thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lyndon 1871 F pulseaudio /dev/snd/controlC0: lyndon 1871 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 11:18:18 2020 InstallationDate: Installed on 2020-04-03 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5585 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.4 dmi.board.name: 0N999T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 2.4.4 dmi.modalias: dmi:bvnDellInc.:bvr2.4.4:bd11/12/2019:svnDellInc.:pnInspiron5585:pvr2.4.4:rvnDellInc.:rn0N999T:rvrA00:cvnDellInc.:ct10:cvr2.4.4: dmi.product.family: Inspiron dmi.product.name: Inspiron 5585 dmi.product.sku: 092B dmi.product.version: 2.4.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872510] [NEW] Slow / Broken Boot on Battery Power
Public bug reported: The behavior is the same booting from USB to install the OS, and booting from NVMe on an installed OS. I'm using disk encryption, but I don't believe it plays a factor. When I boot plugged in to power, the system behaves normally, even once battery is disconnected. I can put the system to sleep on battery, wake on battery, and everything is fine. The initial boot on battery just does not seem happy either way. I've tried both with and without TLP installed. This behavior was present on 18.04, but I assumed it was an "old kernel" issue as this is fairly new hardware. I was previously on Manjaro w/ kernel 5.4, and the system was fine, but using Focal Fossa on kernel 5.4 presents the boot issue. It appears to get through most of the boot process but I don't ever see the login screen, it sits hung at a black screen and a mouse. Overall the boot process itself feels very sluggish. Please let me know if there's more information I can provide - thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lyndon 1871 F pulseaudio /dev/snd/controlC0: lyndon 1871 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 11:18:18 2020 InstallationDate: Installed on 2020-04-03 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5585 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.4 dmi.board.name: 0N999T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 2.4.4 dmi.modalias: dmi:bvnDellInc.:bvr2.4.4:bd11/12/2019:svnDellInc.:pnInspiron5585:pvr2.4.4:rvnDellInc.:rn0N999T:rvrA00:cvnDellInc.:ct10:cvr2.4.4: dmi.product.family: Inspiron dmi.product.name: Inspiron 5585 dmi.product.sku: 092B dmi.product.version: 2.4.4 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- 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/1872510 Title: Slow / Broken Boot on Battery Power Status in linux package in Ubuntu: Confirmed Bug description: The behavior is the same booting from USB to install the OS, and booting from NVMe on an installed OS. I'm using disk encryption, but I don't believe it plays a factor. When I boot plugged in to power, the system behaves normally, even once battery is disconnected. I can put the system to sleep on battery, wake on battery, and everything is fine. The initial boot on battery just does not seem happy either way. I've tried both with and without TLP installed. This behavior was present on 18.04, but I assumed it was an "old kernel" issue as this is fairly new hardware. I was previously on Manjaro w/ kernel 5.4, and the system was fine, but using Focal Fossa on kernel 5.4 presents the boot issue. It appears to get through most of the boot process but I don't ever see the login screen, it sits hung at a black screen and a mouse. Overall the boot process itself feels very sluggish. Please let me know if there's more information I can provide - thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lyndon 1871 F pulseaudio /dev/snd/controlC0: lyndon 1871 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 11:18:18 2020 InstallationDate: Installed on 2020-04-03 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5585 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fres
