-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kdump over NFS fails for f41 #52
Comments
We were not testing this until recently [1] so it slipped through. Upstream issue : rhkdump/kdump-utils#52 [1] coreos/coreos-assembler#3911
We were not testing this until recently [1] so it slipped through. Upstream issue : rhkdump/kdump-utils#52 [1] coreos/coreos-assembler#3911
I find downgrading systemd to systemd-stable-255.10 on F41 could make kdump work again. Note I built systemd-stable-255.10 from source as latest systemd on F41 is v256. |
The other thing I find is that ls -lh /dev/disk/by-path/ |grep pci-0000:04:00.0-part$
drwxr-xr-x. 7 root root 140 Oct 25 03:18 pci-0000:04:00.0-part On f40: ls -lh /dev/disk/by-path/ |grep pci-0000:04:00.0-part$
echo $?
1 |
This symbol link is created by For unmounted nfs, dracut cannot determine it's fstype findmnt -e -v -n -o 'FSTYPE' --source "$_find_dev" and dracut will use 0:0 as its maj:min, unfortunately, the output of stat -L -c '%t:%T' /dev/disk/by-path/pci-0000:04:00.0-part/ is also 0:0, so dracut treats them as the same device and writes the latter as a persistent name to the I think this bug consists of three parts:
These factors together cause the second kernel to wait for an impossible task - mounting /dev/disk/by-path/pci-0000:04:00.0-part/ |
This way we have good coverage of most-used kdump features. Some context on the NFS kdump configuration: coreos/fedora-coreos-tracker#1729 This was previously merged in [1] then reverted in [2] because the nfs server container was not multi-arch, causing the pipeline to trip on it. It's also not functionning on systemd256 (so anything f41 and above), see [3] This requires coreos#3917 for the multi-arch container, and coreos#3921 [1] coreos@b10d8dc [2] coreos@af1468c [3] rhkdump/kdump-utils#52
This way we have good coverage of most-used kdump features. Some context on the NFS kdump configuration: coreos/fedora-coreos-tracker#1729 This was previously merged in [1] then reverted in [2] because the nfs server container was not multi-arch, causing the pipeline to trip on it. It's also not functionning on systemd256 (so anything f41 and above), see [3] This requires coreos#3917 for the multi-arch container, and coreos#3921 [1] coreos@b10d8dc [2] coreos@af1468c [3] rhkdump/kdump-utils#52
Using the following config in fedora coreOS 41 :
The initramfs indefinitely wait after mounting
kdumproot.mount
:using kexec-tools-2.0.29-1
I tried to downgrade
nfs-utils-coreos
to the f40 rpm but it does not fix the issue.The same setup works fine in F40.
The text was updated successfully, but these errors were encountered: