[Kernel-packages] [Bug 2051418] Re: installed linux-image-6.5.0-15-generic package post-installation script subprocess returned error exit status 1
Software index is broken. It is impossible to install or remove any software. ** Attachment added: "Screenshot from 2024-02-03 10-04-31.png" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2051418/+attachment/5744386/+files/Screenshot%20from%202024-02-03%2010-04-31.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051418 Title: installed linux-image-6.5.0-15-generic package post-installation script subprocess returned error exit status 1 Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: Here is the error when trying to upgrade Ubuntu: $ sudo apt-get autoremove [sudo] password for XXX: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: linux-image-6.5.0-14-generic 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 14.3 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 248924 files and directories currently installed.) Removing linux-image-6.5.0-14-generic (6.5.0-14.14) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-6.5.0-14-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' /usr/sbin/grub-mkconfig: 12: /etc/default/grub: processor.max_cstate=1: not found run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127 dpkg: error processing package linux-image-6.5.0-14-generic (--remove): installed linux-image-6.5.0-14-generic package post-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: linux-image-6.5.0-14-generic Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-gl-535_535.113.01-0ubuntu3_amd64.deb ./casper/minimal.standard.live.squashfs CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sat Jan 27 10:39:26 2024 InstallationDate: Installed on 2023-10-29 (90 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: subiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2051418/+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 2052323] [NEW] Azure Site Recovery Disk Filter Driver (ASRDFD) DKMS module
You have been subscribed to a public bug: The Azure Site Recovery Disk Filter Driver is used for Azure site disaster recovery to aid in data replication and recovery. Microsoft has requested that the driver be made available as a DKMS module in generic and Azure kernels. ** Affects: linux-meta-azure (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Azure Site Recovery Disk Filter Driver (ASRDFD) DKMS module https://bugs.launchpad.net/bugs/2052323 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-azure in Ubuntu. -- 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 2052323] Re: Azure Site Recovery Disk Filter Driver (ASRDFD) DKMS module
** Package changed: ubuntu => linux-meta-azure (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052323 Title: Azure Site Recovery Disk Filter Driver (ASRDFD) DKMS module Status in linux-meta-azure package in Ubuntu: New Bug description: The Azure Site Recovery Disk Filter Driver is used for Azure site disaster recovery to aid in data replication and recovery. Microsoft has requested that the driver be made available as a DKMS module in generic and Azure kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-azure/+bug/2052323/+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 2051418] Re: installed linux-image-6.5.0-15-generic package post-installation script subprocess returned error exit status 1
Self solved the issue by deactivating: processor.max_cstate=1 in grub: $ sudo nano /etc/default/grub GNU nano 7.2/etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=hidden GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash processor.max_cstate=1" GRUB_CMDLINE_LINUX="" #processor.max_cstate=1 # If your computer has multiple operating systems installed, then you # probably want to run os-prober. However, if your computer is a host # for guest OSes installed via LVM or raw disk devices, running # os-prober can cause damage to those guest OSes as it mounts # filesystems to look for things. #GRUB_DISABLE_OS_PROBER=false CTRL + O > Rertun CTRL + X $ sudo grub-mkconfig -o /boot/grub/grub.cfg No clue however about this error message: /usr/sbin/grub-mkconfig: 12: /etc/default/grub: processor.max_cstate=1: not found -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051418 Title: installed linux-image-6.5.0-15-generic package post-installation script subprocess returned error exit status 1 Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: Here is the error when trying to upgrade Ubuntu: $ sudo apt-get autoremove [sudo] password for XXX: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: linux-image-6.5.0-14-generic 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 14.3 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 248924 files and directories currently installed.) Removing linux-image-6.5.0-14-generic (6.5.0-14.14) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-6.5.0-14-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' /usr/sbin/grub-mkconfig: 12: /etc/default/grub: processor.max_cstate=1: not found run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127 dpkg: error processing package linux-image-6.5.0-14-generic (--remove): installed linux-image-6.5.0-14-generic package post-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: linux-image-6.5.0-14-generic Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-gl-535_535.113.01-0ubuntu3_amd64.deb ./casper/minimal.standard.live.squashfs CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sat Jan 27 10:39:26 2024 InstallationDate: Installed on 2023-10-29 (90 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: subiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2051418/+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 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
Well, I have the same problem as the original post except I am running, but I can't get rid of the trying to install loop. It fails to reinstall when updating other packages. zfs version zfs-2.1.5-1ubuntu6~22.04.2 zfs-kmod-2.2.0-0ubuntu1~23.10 -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To recreate: - Install Ubuntu 22.04.3. - Update to current. - Install package 'zfs-dkms' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+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 2006557] Re: Enable rdma-sniffer for libpcap
** Changed in: libpcap (Ubuntu) Status: In Progress => Fix Committed -- 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/2006557 Title: Enable rdma-sniffer for libpcap Status in libpcap package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Invalid Status in libpcap package in Debian: Won't Fix Bug description: Hi, The request is to build and configure stock package libpcap with rdma-sniffer enabled. We'd like users of rdma devices to be able to sniff on them using stock tcpdump. Currently when using default tcpdump It does not list rdma devices. $ tcpdump -D |grep -i rdma $ when using locally build tcpdump (with rdma enabled) $ cd $ ./tcpdump -D |grep -i rdma 24.rocep4s0 (RDMA sniffer) 25.rocep7s0f0 (RDMA sniffer) 26.rocep7s0f1 (RDMA sniffer) 27.rocep10s0f0 (RDMA sniffer) 28.rocep10s0f1 (RDMA sniffer) 29.rocep33s0f0 (RDMA sniffer) 30.rocep33s0f1 (RDMA sniffer) 31.rocep36s0f0 (RDMA sniffer) 32.ibp36s0f1 (RDMA sniffer) Locally build steps: clone sources: $ mkdir tcpdumpbuild $ cd tcpdumpbuild/ $ git clone https://github.com/the-tcpdump-group/tcpdump.git $ git clone https://github.com/the-tcpdump-group/libpcap.git install required packages (including rdma packages so libpcap is built with rdma enabled): $ apt install flex bison librdmacm-dev librdmacm1 rdma-core rdmacm-utils configure and build $ cd libpcap $ ./autogen.sh $ ./configure --enable-rdma=yes $ make cd ../tcpdump/ ./autogen.sh ./configure $ make now ./tcpdump -D can show rdma devices. Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpcap/+bug/2006557/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
** Also affects: util-linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: Fix Released ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: New Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2052013] Re: NVMe high power state after wake up from sleep
** Description changed: [ISSUE] I have a dual boot acer helios laptop (windows is on the nvme, ubuntu on - an SSD). Once I boot into Ubuntu (SSD) my drive works as expected. + an SSD). Once I boot into Ubuntu (SSD) my nvme drive works as expected. But once I set my laptop to sleep and wake it back up again the nvme drive power state is set to max rather than the default low power state. This causes a lot of heat to be generated and the smartctl tool reports the tempSenor#2 as 80-90C when in low power mode it runs at 40-60C. I've observed this behaviour under Ubuntu 20.04.6 LTS and via live USB (22.04.3 LTS, 23.10) BEFORE SLEEP: sudo nvme get-feature /dev/nvme0n1p1 -f 2 -H get-feature:0x2 (Power Management), Current value:0x04 Workload Hint (WH): 0 - No Workload Power State (PS): 4 AFTER SLEEP: sudo nvme get-feature /dev/nvme0n1p1 -f 2 -H get-feature:0x2 (Power Management), Current value: Workload Hint (WH): 0 - No Workload Power State (PS): 0 [Fix] If i run the following command i can manually set the drive into a low power mode which dramatically effects both the onboard nvme temps and system temp (PCH chip) sudo nvme set-feature /dev/nvme0n1p1 -f 2 -v 4 [INFO] cat /etc/os-release NAME="Ubuntu" VERSION="20.04.6 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.6 LTS" VERSION_ID="20.04" VERSION_CODENAME=focal UBUNTU_CODENAME=focal sudo nvme get-feature /dev/nvme0n1p1 -f 0x0c -H get-feature:0xc (Autonomous Power State Transition), Current value:0x01 Autonomous Power State Transition Enable (APSTE): Enabled sudo smartctl /dev/nvme0n1p1 -a smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.15.0-92-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: SAMSUNG MZVL2512HCJQ-00B07 Serial Number: <> Firmware Version: GXA7302Q PCI Vendor/Subsystem ID:0x144d IEEE OUI Identifier:0x002538 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 6 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Utilization:200,490,106,880 [200 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64:002538 b211b0a1d9 Local Time is: Thu Feb 1 22:18:19 2024 PST Firmware Updates (0x16):3 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x0057): Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 81 Celsius Critical Comp. Temp. Threshold: 85 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 8.37W --0 0 0 00 0 1 + 8.37W --1 1 1 10 200 2 + 8.37W --2 2 2 20 200 3 - 0.0500W --3 3 3 3 20001200 4 - 0.0050W --4 4 4 4 5009500 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature:43 Celsius Available Spare:100% Available Spare Threshold: 10% Percentage Used:0% Data Units Read:5,771,370 [2.95 TB] Data Units Written: 6,509,044 [3.33 TB] Host Read Commands: 96,282,996 Host Write Commands:92,199,213 Controller Busy Time: 56 Power Cycles: 1,245 Power On Hours: 2,632 Unsafe Shutdowns: 145 Media and Data Integrity Errors:3 Error Information Log Entries: 0 Warning Comp. Temperature Time:0 Critical Comp. Temperature Time:0 Temperature Sensor 1: 43 Celsius Temperature Sensor 2: 42 Celsius Thermal Temp. 1 Transition Count: 3 Thermal Temp. 1 Total Time: 240 Error Information (NVMe Log 0x01, max 64 entries) No Errors Logged -- 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/2052013 Title: NVMe high power state after wake up f
[Kernel-packages] [Bug 2049634] Re: SMB 1 broken in kernel 6.5.0.14.14~22.04.7
I just realised that the offset to the first hole matches the default wsize=16580 argument for SMB 1.0 mounts, or at least that is what "mount -l" reports. That is, cifs is writing each time wsize bytes with the right data + a hole of 3900 bytes made of binary zeros. And the next blocks look the same: wsize bytes with the right data + a hole of 3900 bytes each time. As noted above, the distance between the "wsize + hole" areas is 20480, which is wsize=16580 + the hole size of 3900 bytes. For the record, the connection is using RawNTLMSSP, documented as "NTLMSSP without SPNEGO, NTLMv2 hash". -- 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/2049634 Title: SMB 1 broken in kernel 6.5.0.14.14~22.04.7 Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Bug description: Hi all: I upgraded my Ubuntu yesterday and automatically got the newer Linux Kernel version 6.5.0-14-generic #14~22.04.1-Ubuntu. Previously, I was running kernel version 6.2 . I still have a legacy system on the network using SMB protocol version 1.0. With the new kernel version, copying files does not work reliably anymore. Some random byte blocks in the destination files are overwritten with binary zeros. It happens quite often. This is not the first time the Linux guys temporarily break SMB protocol version 1.0, see for example this bug report of mine: https://bugs.launchpad.net/ubuntu/+bug/2033732 I checked package linux-image-generic-hwe-22.04 with Synaptic, and now it lists just 2 versions: 6.5.0.14.14~22.04.7 (jammy-updates) 5.15.0.25.27 (jammy) Is there a way to go back to the latest 6.2 kernel version? How do I prevent Ubuntu from upgrading to 6.5 next time around? I have searched the Internet, but I haven't found yet a usable answer. I don't want to go back all the way to Kernel 5.15 if I can avoid it. Thanks in advance, rdiez To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+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 2042841] Re: Snapshots of encrypted zfs 2.1.5 filesystems sometimes broken
[Expired for zfs-linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Expired -- 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/2042841 Title: Snapshots of encrypted zfs 2.1.5 filesystems sometimes broken Status in zfs-linux package in Ubuntu: Expired Bug description: As reported in https://github.com/openzfs/zfs/issues/15474 -- I have had occasional broken snapshots with ZFS 2.1.5 on Jammy on encrypted filesystems. This is _not_ the same problem as https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190 **Manifestation** # ls -l /var/lib/mysql/redacted/.zfs/snapshot/planb-20231101T0500Z ls: cannot access '/var/lib/mysql/redacted/.zfs/snapshot/planb-20231101T0500Z/aria_log.0001': Input/output error ls: cannot access '/var/lib/mysql/redacted/.zfs/snapshot/planb-20231101T0500Z/aria_log_control': Input/output error total 10129 -? ? ? ? ?? aria_log.0001 -? ? ? ? ?? aria_log_control -rw-rw 1 mysql mysql 0 nov 1 02:55 ddl.log -rw-rw 1 mysql mysql 16384 okt 17 10:26 ddl_recovery.log -rw-rw 1 mysql mysql 10737419544 nov 1 02:55 galera.cache -rw-rw 1 mysql mysql 8 okt 17 10:26 galera.pid ... Creating newer snapshots succeeded just fine, but this snapshot was unreadable: each and every file in in it was not readable (except for 0-sized files). Trying to 'zfs send' this snapshot failed as well. **Workaround** Deleting the snapshot worked. But at some point a new snapshot would be broken again. **Fix** Upgrading to 2.1.13 -- as described in the Github ticket -- fixed the problem. Cheers, Walter Doekes OSSO B.V. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2042841/+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
