You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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%.
The text was updated successfully, but these errors were encountered:
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.
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.
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%.
The text was updated successfully, but these errors were encountered: