No space left on device during during extracting the tar file

...
Cache Size: ~9302 MB (9753348013 B)
/usr/bin/tar -xf /home/runner/work/_temp/df03d4e4-948e-4053-be7b-a08c6d648879/cache.tzst -P -C /home/runner/work/returnn/returnn --use-compress-program unzstd
/usr/bin/tar: ../../../.local/lib/python3.8/site-packages/nvidia/cublas/lib/libcublasLt.so.12: Wrote only 1536 of 10240 bytes
...
/usr/bin/tar: ../../../.local/lib/python3.8/site-packages/nvidia/cublas/include/__pycache__: Cannot mkdir: No such file or directory
/usr/bin/tar: ../../../.local/lib/python3.8/site-packages/nvidia/cublas/include/__pycache__/__init__.cpython-38.pyc: Cannot open: No such file or directory
/usr/bin/tar: ../../../.local/lib/python3.8/site-packages/nvidia/cublas/include: Cannot mkdir: No space left on device

(Note: related is also #1658, no space left on device during creating the tar file.)

I'm not sure about the best option how to solve this. For exampe:

• There could be an option to make this a warning instead of an error. Maybe, also, when this happens, it would clean it up again.

Start with the /usr/bin/tar extraction log in this issue and compare it with related issue #1658. The issue does not name a file, test, or agreed behavior; clarify whether extraction failures should be warnings or errors and what cleanup or disk-space handling would count as done.