bug: /proc/kcore prevents cloning / copy operations due to how much space it appears to take up

[Tbusk]

What Happened?

Before, when attempting to clone a disk (for backup), it errored out saying the drive is over 140TB in size and not enough space in the next drive (my root is like ~100gb for reference). I looked for the cause of this, and it turns out the file kcore in /proc/ is the culprit.

Steps to Reproduce

1. Go to /proc/
2. Find kcore near bottom.

Expected Behavior

Cloning / transfer / copy operations work from a smaller drive to a larger one without a hitch.

OS Version

8.x (Circe)

OS Architecture

amd64 (on most hardwares)

Session Type

Classic Session (X11, This is the default)

Software Version

Latest release (I have run all updates)

Log Output

Hardware Info

No response

[jeremypw]

Nautilus and Dolphin also show large apparent size for this pseudo file (Nautilus shows the same as Files while Dolphin shows about 120TB.

More about this can be found at https://askubuntu.com/questions/587531/absurdly-large-proc-kcore-file-what-does-it-mean. I do not think it is a Files issue particularly. As it is a pseudo-file its size has no physical meaning. It looks like it representing the address space rather than the actual size of the physical memory.