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: CLOSED EOL
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: 2024-05-21 14:47 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-21 14:47:44 UTC
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

Comment 2 Aoife Moloney 2024-05-07 16:13:41 UTC
This message is a reminder that Fedora Linux 38 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '38'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 38 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Aoife Moloney 2024-05-21 14:47:44 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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