Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script destroyed my OS -> C drive is a bad idea for cache #188

Open
MetzgerGeorg opened this issue May 14, 2024 · 4 comments
Open

Script destroyed my OS -> C drive is a bad idea for cache #188

MetzgerGeorg opened this issue May 14, 2024 · 4 comments

Comments

@MetzgerGeorg
Copy link

My C drive is rather small, with less than 10GB of free space.
When executing the Tiny11 script, all files were extracted to C drive and processed there until it was completely full.
It would be MUCH better to use the local Tiny11 script folder as cache directory.

Also, when I killed the process because it did not continue (disk full), I was left with a "C:\scratchdir" folder that said it was 30GB in size.
I assume there are some hard- or softlinks inside this folder that pointed to the "real" folders on C and after deleting the folder (or TRYING) to delete, my personal files were gone.

So, effectively, my system was trashed.

Recommendations:
Add some clean-up possibility to remove remnants of a failed run
Use local folder, not root of C!

@MetzgerGeorg
Copy link
Author

Sorry, looks like my post is a copy of #183 partly...
Anyway, request for clean-up feature remains valid...

@Elrondo46
Copy link
Contributor

Don't had this problem. Had to deleted this directory one time without issues

@eugenesan
Copy link
Contributor

#183 is indeed related and if resolved will mitigate the problem described here.

I recommend closing this issue as a duplicate and add this issue as a use case.

@rcmaehl
Copy link
Contributor

rcmaehl commented May 19, 2024

Proposed #194

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants