Hi Coiby,
On Wed, 26 Oct 2022 11:32:30 +0800
Coiby Xu <coxu(a)redhat.com> wrote:
On Thu, Oct 20, 2022 at 04:14:30PM +0800, Tao Liu wrote:
>Hi Coiby,
>
>On Thu, Oct 20, 2022 at 2:41 PM Coiby Xu <coxu(a)redhat.com> wrote:
>>
>> Hi Tao,
>>
>> This test can't run on F35, right?
>>
>Yes, the test cannot be run on f35. It requires dracut >=057, because
>the 80lvmthinpool-monitor is integrated in 057.
I tried the test three times this week on Fedora-Cloud-Base-36-1.5.x86_64.qcow2
but it failed all times. One time I ran it locally and here are the
logs,
[ 1.601263] kdump[517]: saving to
/kdumproot/mnt/var/crash/127.0.0.1-2022-10-26-02:59:23/
[ 1.607605] kdump[522]: saving vmcore-dmesg.txt to
/kdumproot/mnt/var/crash/127.0.0.1-2022-10-26-02:59:23/
[ 1.617199] kdump[528]: saving vmcore-dmesg.txt complete
[ 1.619315] kdump[530]: saving vmcore
[ 1.761168] device-mapper: thin: 253:2: reached low water mark for data device:
sending event.
[ 1.826916] device-mapper: thin: 253:2: switching pool to out-of-data-space (queue IO)
mode
Copying data : [100.0 %] | eta: 0s
[ 1.928425] kdump.sh[531]: The kernel version is not supported.
[ 1.929227] kdump.sh[531]: The makedumpfile operation may be incomplete.
Found a vmcore dir "/mnt/var/crash/127.0.0.1-2022-10-26-02:59:23":
Failed to retrive dmesg from vmcore!
kexec-kdump-test: TEST FAILED
Vmcore missing
I can confirm dracut-057-3.fc36.x86_64 has already been installed.
Interestingly last week I ran the test on f36, it actually succeeded
https://github.com/coiby/kexec-tools/actions/runs/3318507193/jobs/5482528377
on first sight this looks more like some kernel change to F36 broke
makedumpfile. Have you tried it with a different core collector other
than makedumpfile?
Thanks
Philipp