Bug 2190432 - Failing to boot after upgrade to Fedora 38: "device-mapper:cache: bad config value for cleaner: 1"
Summary: Failing to boot after upgrade to Fedora 38: "device-mapper:cache: bad config ...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: lvm2
Version: 38
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: LVM Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-28 12:07 UTC by Rolf Fokkens
Modified: 2023-08-02 02:20 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
Screenshot boot crash (155.79 KB, image/jpeg)
2023-04-28 12:09 UTC, Rolf Fokkens
no flags Details

Description Rolf Fokkens 2023-04-28 12:07:36 UTC
After upgrading to Fedora 38 my system failed to boot. An on-screen Stack Trace was the result, headed by the line:

device-mapper:cache: bad config value for cleaner: 1

This was clearly not a kernel problem, because the same kernel for Fedora 37 was still booting fine. Must be a userspace problem, possbly dracut but more likely lvm.

After removing a cachesettings "cleaner=1" the system was able to boot again. Unfortunately this was not trivial, both these failed:

lvchange --cachesettings "" /dev/base/lukscache
lvchange --cachesettings "default" /dev/base/lukscache

The only way to fix this was:
- vgcfgbackup
- remove the cleaner=0 setting in the backup file
- vgcfgrestore

Reproducible: Always

Steps to Reproduce:
1. Have a running Fedora 37 systeme with lvm-cache with cachesettings "cleaner=1"
2. Upgrade to Fedora 38
3. Try to boot
Actual Results:  
Boot failure

Expected Results:  
Booting system

For me this is no urgent matter because all is working again, but a less knowledgeable user may be stuck with a broken system.

Comment 1 Rolf Fokkens 2023-04-28 12:09:56 UTC
Created attachment 1960802 [details]
Screenshot boot crash


Note You need to log in before you can comment on or make changes to this bug.