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

Change from lazy media storage cleanup to eager #677

Merged
merged 1 commit into from
Mar 27, 2024

Conversation

andrey-utkin
Copy link
Contributor

Before, if there was any storage location below max use threshold, the cleanup was skipped. This might cause problem described in #656 : as long as one location has space, others might fill up if used by other processes. The default location, /var/lib/bluecherry/recordings/ is usually on the system rootfs, where many services' and users' activities contribute to increasing the filesystem space used.

Now, the media cleanup happens if any of the storage locations is over the threshold.

Before, if there was any storage location below max use threshold, the
cleanup was skipped. This might cause problem described in
bluecherrydvr#656 :
as long as one location has space, others might fill up if used by other
processes. The default location, /var/lib/bluecherry/recordings/ is
usually on the system rootfs, where many services' and users' activities
contribute to increasing the filesystem space used.

Now, the media cleanup happens if any of the storage locations is over
the threshold.
@andrey-utkin
Copy link
Contributor Author

Tested, works.

@andrey-utkin andrey-utkin merged commit 4dd34d5 into bluecherrydvr:master Mar 27, 2024
2 checks passed
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

Successfully merging this pull request may close these issues.

1 participant