Bug 2190432

Summary: Failing to boot after upgrade to Fedora 38: "device-mapper:cache: bad config value for cleaner: 1"
Product: [Fedora] Fedora Reporter: Rolf Fokkens <rolf>
Component: lvm2Assignee: LVM Team <lvm-team>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 38CC: agk, anprice, bmarzins, bmr, cfeist, heinzm, kzak, lvm-team, mcsontos, prajnoha, zkabelac
Target Milestone: ---Keywords: Desktop, Regression, Upgrades
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot boot crash none

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