--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: debian-boot: Please include dm-cache in rescue kernel
- From: Nagy Attila <nagy.attila.gabor@gmail.com>
- Date: Wed, 01 Jun 2022 11:52:10 +0200
- Message-id: <165407713064.27345.13533535645883769785.reportbug@demo.office.wildom.com>
Package: debian-boot
Version: 4.19.0-20-amd64
Severity: wishlist
Dear Maintainer,
Please include dm-cache and possibly all dm-* modules in the rescue kernel. The lack of these modules
makes the rescue process very complicated for a sytem where dm-cache was
applied to an important logical volume.
* What led up to the situation?
We are using LVM2 and an dm-cache to speed up some of the volumes with SSD that are
run on HDD-s. We had an issue where we could not boot the system, so as
normally we turned to the rescue mode of the installer to reinstall the boot
partition and parts of the kernel. Unfortunately the /var partition is
backed up by lvm-cache and the rescue disk was not able to bring it up.
* What exactly did you do (or not do) that was effective (or ineffective)?
We tried several ways to load the missing modules from the installer, but
were not able to find any.
As a last resolt we were able to find a rescue disk matching the exact
kernel version the system was on, so we could load the kernel modules from
the still accessible logical volumes.
* What was the outcome of this action?
We were able to recover the system, but the process was much more
complicated than it normally would.
* What outcome did you expect instead?
Because dm-cache and the relevant modules are part of the official debian
kernel package (linux-image-4.19.0-20-amd64) we expected these modules
readily be available for the rescue kernel as well.
An alternative, but more complication solution would be if the installer
would detect these types of LVs and download the driver automatically or
upon request.
Thank you
-- System Information:
Debian Release: 10.12
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-20-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=hu_HU.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a (very) old kernel or the bug is old itself
without resolution. Maybe it was for a feature enablement which nobody
acted on. We are sorry we were not able to timely deal with this issue.
There are many open bugs for the src:linux package and thus we are
closing older bugs where it's unclear if they still occur in newer
versions and are still relevant to the reporter. For an overview see:
https://bugs.debian.org/src:linux .
If you can reproduce your issue with
- the current version in unstable/testing
- the latest kernel from backports
or, if it was a feature addition/wishlist and still consider it
relevant, then:
Please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Please try to provide as much fresh details including kernel logs where
relevant. In particular were an issue is coupled with specific hardware we
might ask you to do additional debugging on your side as the owner of the
hardware.
Regards,
Salvatore
--- End Message ---