-
Notifications
You must be signed in to change notification settings - Fork 76
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
Temporary backup files not always cleaned up #326
Comments
hmm. i use maybe there's been an update that fixes this? |
also there is no guarantee, afaik, that upon calling dispose from userland the tmpdata will immediately go away. i think it's up to the OS when it happens. |
That occurred to me as a possibility. There were 5 directories when I cleared it earlier and I /think/ it's been more than 5 days (so 5 backups) since I last did it but I'm not sure. I didn't think to do the things in the checklist before I deleted which is why I've filed the issue. I vaguely remember doing check 3 but I didn't write down any notes so I'm not sure. |
A backup has successfully run since the last message and there are no leftover tmp files. However, my manual clearing of the tmp directory left the server in a bad state resulting in this Sentry error (credentials needed). It looks like the tmp library may have been remembering a subdirectory it created previously and expecting to put files there. I wouldn't expect that to cause a crash. When I look at the tmp directory now ( |
Our QA server at https://test.central.getodk.org/ now has a ~7GB database. Its harddrive periodically fills up and I've identified that this is because of temporary backup files that stick around. It doesn't look like every backup attempt leaves temporary files behind and I haven't figured out why/when it happens.
The only way I know how to recover is to go to
/var/lib/docker/overlay2
, rundu -a | sort -n -r | head -n 10
to identify the biggest directories, go to thetmp
directory for the biggest ones and clear out anything there.Here are some ideas for trying to troubleshoot:
The text was updated successfully, but these errors were encountered: