Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
404 when using limitedStore and hitting the storage limit #249
Running in docker, with arguments:
Thanks for reporting this! I was able to reproduce this by creating uploads until the data store hit the specified limit. After that I deleted some files from the data directory. Now, tusd is not able to delete some old uploads when it tries to reclaim disk space for new uploads.
It seems as if you have another service/user which deletes files from the data directory and collided with tusd. This should be fixed in the latest commit in the master branch, please test it out and tell me if it fixes your problem.
BTW, we are considering dropping support for the limitedstore package in the next major version (see #212). Due to limitedstore's design, it is not able to persist the internal state between restarts and therefore is not able to cleanup files which were created by previous tusd processes. Furthermore, limitedstore only works if you only have a single tusd process running, which is rarely the case. We have had problems with these limitations in the past and therefore have never used it in production. We also recommend you to reconsider your setup, even if the next major version will take some more time.
Ahhhh, I had manually deleted some images after doing initial testing with it. My bad, thanks!
I understand that this isn't the ideal setup. This was a quick test run to see if