| Summary: | Ark fails due to spurious "no space left on device" error | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Jan Stolarek <jwstolarek> |
| Component: | tdeutils | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | bugwatch, jwstolarek, michele.calgaro |
| Priority: | P5 | ||
| Version: | R14.0.x [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2968 | ||
|
Description
Jan Stolarek
2020-04-16 07:37:11 CDT
Hi Jan, I agree with you it may be related to some temporary files. Any way you can monitor the free space while the extraction process is in progress? This could give some extra pointers for troubleshooting. I just checked - Ark extracts the files to a temporary location in /tmp/tde-USER/arkXXX/extremoteXXX, where XXX are random strings, and then copies the files from temporary location to target location. Thanks for checking Jan. I will leave the bug open to remind that the code could be optimize and extract the files in the actual final folder rather then a temp location first, if possible. Correct me if I'm wrong, but Ark does not implement its own extraction algorithms but only acts as a frontend for extraction tools installed on the system. If that is the case then it shouldn't be too difficult to do for most format archives as their extraction seems to work in place. Hi Jan, you are correct, Ark is just a front end. I can't really say how long it would take to fix this before looking at the code :-) |