Bug 2357959
| Summary: | kdump fails to generates initrd with default config | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Marius Vollmer <mvollmer> |
| Component: | kdump-utils | Assignee: | Lichen Liu <lichliu> |
| Status: | NEW --- | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 42 | CC: | coxu, lichliu, mpitt |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | --- | Flags: | lichliu:
mirror+
|
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | CockpitTest | ||
| 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: | |||
|
Description
Marius Vollmer
2025-04-07 15:32:33 UTC
I just spent an hour investigating this in https://github.com/linux-system-roles/kdump/pull/233#issuecomment-2800567079 . This is hilariously hard to debug. Even KDUMP_STDLOGLVL=3 KDUMP_SYSLOGLVL=3 KDUMP_KMSGLOGLVL=3 sh -x kdumpctl start doesn't give something useful. Calling /sbin/mkdumprd -f /boot/initramfs-6.14.0-63.fc42.x86_64kdump.img 6.14.0-63.fc42.x86_64 fails completely silently, and running that with `sh -x` is inscrutable. Thanks Marius for investigating! (In reply to Martin Pitt from comment #1) > I just spent an hour investigating this in > https://github.com/linux-system-roles/kdump/pull/233#issuecomment-2800567079 > . This is hilariously hard to debug. Even > > KDUMP_STDLOGLVL=3 KDUMP_SYSLOGLVL=3 KDUMP_KMSGLOGLVL=3 sh -x kdumpctl > start > > doesn't give something useful. Calling > > /sbin/mkdumprd -f /boot/initramfs-6.14.0-63.fc42.x86_64kdump.img > 6.14.0-63.fc42.x86_64 > > fails completely silently, and running that with `sh -x` is inscrutable. > Thanks Marius for investigating! Hi Martin, Debugging with `debug=1 kdumpctl rebuild`, I think this issue happens because kdump does not support btrfs subvol now. (In reply to Lichen Liu from comment #2) > I think this issue happens because kdump does not support btrfs subvol now. If you don't want to support it, please make it fail with a clear error message. Don't send people on wild goose chases, please. (In reply to Marius Vollmer from comment #3) > (In reply to Lichen Liu from comment #2) > > I think this issue happens because kdump does not support btrfs subvol now. > > If you don't want to support it, please make it fail with a clear error > message. Don't send people on wild goose chases, please. OK, I think we can keep this bug for improving the error messages. For btrfs support, I don't have a plan to support it now, but I have added it to the future feature list. (In reply to Marius Vollmer from comment #3) > (In reply to Lichen Liu from comment #2) > > I think this issue happens because kdump does not support btrfs subvol now. > > If you don't want to support it, please make it fail with a clear error > message. Don't send people on wild goose chases, please. Hi Marius, we added basic btrfs support in kdump-uitls 1.0.59, it works on Fedora SilverBlue with the default configuration, can you help to test this issue? Thanks, Lichen *** Bug 2306035 has been marked as a duplicate of this bug. *** |