From d4dab9b740170b327046c1c63038903daa1917ad Mon Sep 17 00:00:00 2001 From: Kai Curry Date: Mon, 9 Feb 2026 17:12:07 -0100 Subject: [PATCH] link back to recordings for troubleshooting --- docs/docs/configuration/storage.md | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/docs/docs/configuration/storage.md b/docs/docs/configuration/storage.md index 8d2787814..2e3533c46 100644 --- a/docs/docs/configuration/storage.md +++ b/docs/docs/configuration/storage.md @@ -135,15 +135,6 @@ This avoids the CPU cost of scanning an empty filesystem and avoids tripping the Each of these paths can be on a different filesystem via bind mounts. Frigate's System page reports disk usage independently for recordings, clips, and cache using OS-level filesystem stats, so usage will be correct even when paths are on separate mounts. However, only the recordings path is monitored for emergency cleanup — the other paths are managed solely through retention-based expiration. -## Debugging Storage Issues +## Troubleshooting -Enable debug logging for the relevant modules to understand storage behavior: - -```yaml -logger: - logs: - frigate.storage: debug - frigate.record.cleanup: debug - frigate.record.maintainer: debug - frigate.events.cleanup: debug -``` +For issues with recordings not being written to disk fast enough (segment cache warnings, slow copy times, network share performance), see [Recordings Errors](/troubleshooting/recordings).