Invalid check for sufficient disk space during partial extraction

[dtantsur]

The check introduced in #495 seems to take into account the entire archive instead of the file I'm trying to extract. This results in "insufficient disk space" error when extracting a small file from a large archive. I've tried it with both .zip and .tar.gz files, both of which should support on-fly extraction. Opening a file from an archieve works correctly.

Reproducible: Always

Steps to Reproduce:

1. Take an archive with unpacked size more than free space on the disk (8G vs 3G in my case)
2. Try to extract a sufficiently small file (18 MiB in my case)

Actual Results:
An error window with "Insufficient disk space"

Expected Results:
The file is extracted

engrampa-1.28.2-1.fc41.x86_64

[lukefromdc]

This is probably still better than filling an entire filesystem's remaining space with an incomplete file that cannot be opened. This done in /home when /home is in the root FS can cause all kinds of problems, possibly enough that an end user whose system locks up will "nuke from orbit" and reinstall from scratch if they can't get in to delete the partial file and don't know to mount the filesystem from the same bootable USB drive they'd use to reinstall.

At least since I can reproduce this I can test any fix someone codes up.