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

Storage does not always respect setting default (/var/lib/bluecherry/recordings) #656

Closed
curtishall opened this issue Jan 28, 2024 · 1 comment
Assignees

Comments

@curtishall
Copy link
Member

In this test setup on .66 /var/lib/bluecherry/recordings is set to a max of 15% with a 100GB partition. After configuring 256 devices 100% of the disk is used.

I'm not sure if this is related to disk cleanup failing with so many devices or not, however it appears to work mostly fine on /mnt/store (100gb partition) which has priority=1 with max set at 95%.

andrey-utkin added a commit to andrey-utkin/bluecherry-apps that referenced this issue Mar 27, 2024
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 added a commit that referenced this issue Mar 27, 2024
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.
@andrey-utkin
Copy link
Contributor

The situation is no longer observable on that host.
PR #677 (just merged) hopefully fixes it.

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

2 participants