Comment 23 for bug 1970672

I've tested makedumpfile from -proposed on Focal and it looks good to me.

Using a vmcore file with 2TB as an input:

- Original makedumpfile 1.6.7-1ubuntu2.4 fails:

ubuntu@kdump-instance:~$ sudo apt-cache policy makedumpfile
makedumpfile:
  Installed: 1:1.6.7-1ubuntu2.4
  Candidate: 1:1.6.7-1ubuntu2.4
  Version table:
 *** 1:1.6.7-1ubuntu2.4 500
        500 http://phx-ad-3.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1:1.6.7-1ubuntu2 500
        500 http://phx-ad-3.clouds.archive.ubuntu.com/ubuntu focal/main amd64 Packages

ubuntu@kdump-instance:/mnt/202204202351$ makedumpfile -c -d 31 ./vmcore.202204202351 ./dump-incomplete-fabio
The kernel version is not supported.
The makedumpfile operation may be incomplete.
Checking for memory holes : [100.0 %] / __vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(ffffecff81800000) to physical address.
readmem: type_addr: 0, addr:ffffecff81800000, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.

makedumpfile Failed.

- Makedumpfile 1.6.7-1ubuntu2.5 from proposed works:

ubuntu@kdump-instance:~$ sudo apt-cache policy makedumpfile
makedumpfile:
  Installed: 1:1.6.7-1ubuntu2.5
  Candidate: 1:1.6.7-1ubuntu2.5
  Version table:
 *** 1:1.6.7-1ubuntu2.5 500
        500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     1:1.6.7-1ubuntu2.4 500
        500 http://phx-ad-3.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
     1:1.6.7-1ubuntu2 500
        500 http://phx-ad-3.clouds.archive.ubuntu.com/ubuntu focal/main amd64 Packages

ubuntu@kdump-instance:/mnt/202204202351$ makedumpfile -c -d 31 ./vmcore.202204202351 ./dump-incomplete-fabio
The kernel version is not supported.
The makedumpfile operation may be incomplete.
Copying data : [100.0 %] - eta: 0s

The dumpfile is saved to ./dump-incomplete-fabio.

makedumpfile Completed.

It reduced the dump file from 2TB down to 4.5G:

ubuntu@kdump-instance:/mnt/202204202351$ ls -lh vmcore.202204202351
-r-------- 1 ubuntu ubuntu 2.0T Apr 21 2022 vmcore.202204202351

ubuntu@kdump-instance:/mnt/202204202351$ ls -lh dump-incomplete-fabio
-rw------- 1 ubuntu ubuntu 4.5G Dec 12 14:23 dump-incomplete-fabio

The reason for having a vmcore file with the size of the installed RAM in the comment reported by Heather, is that you are forcing makedumpfile to fail, by providing "-c -d 32" (which is a level that doesn't exist, as the max is 31) or moving the makedumpfile binary away, so kdump fails over to cp, which hence will produce the vmcore file with the size of the installed RAM.

Let me know if this is enough to have focal verification concluded.