------- Comment From mihaj...@de.ibm.com 2020-10-01 09:43 EDT------- Took me a bit longer than expected, as I ran into some other unrelated issue. Unfortunately I was not successful. What I did on a pristine Ubuntu 20.04.1 install with a luks-encrypted setup was:
$ add-apt-repository ppa:cascardo/kdump2 $ apt update $ apt install kexec-tools $ apt install kdump-tools The initrd was rebuild and the zipl was run, however zipl.conf wasn't updated with a new crashkernel value and after rebooting it was still the old value of 196 in the kernel command line. Here's the output of dpkg -l for kexec-tools and kdump-tools ii kexec-tools 1:2.0.18-1ubuntu1 s390x tools to support fast kexec r ii kdump-tools 1:1.6.7-4ubuntu1+cascardo2 s390x scripts and tools fo Here's my cryptab content: vda6_crypt UUID=3b1c23fa-0cc4-4ba1-b47e-974f79db1b5c none luks,discard fstab: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> /dev/mapper/vgubuntu-root / ext4 errors=remount-ro 0 1 # /boot was on /dev/vda5 during installation UUID=44950dee-686a-4946-b64e-8b54976d254a /boot ext4 defaults 0 2 /dev/mapper/vgubuntu-swap_1 none swap sw 0 0 lsblk output: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 252:0 0 6G 0 disk ??vda1 252:1 0 512M 0 part ??vda2 252:2 0 1K 0 part ??vda5 252:5 0 731M 0 part /boot ??vda6 252:6 0 4.8G 0 part ??vda6_crypt 253:0 0 4.8G 0 crypt ??vgubuntu-root 253:1 0 3.8G 0 lvm / ??vgubuntu-swap_1 253:2 0 976M 0 lvm [SWAP] Maybe I did something wrong. Let me know. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+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
