administrator/frigate
1
0
Fork 0
mirror of https://github.com/blakeblackshear/frigate.git synced 2026-04-10 00:57:38 +03:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

link back to recordings for troubleshooting

Browse Source
This commit is contained in:
Kai Curry 2026-02-09 17:12:07 -01:00
parent cfd746ae7d
commit d4dab9b740
1 changed files with 2 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/docs/configuration/storage.md
View File

@ -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).