Twice we have seen where the drive appears to fill up but there is no apparent reason for the drive being full. Three of the reasons we have seen so far are caused by 3 different but related issues.
1. Apache errors – for some unknown reason, the Apache log file (located in /var/log/apache2/) grows to an incredible size. Deleting the log file resolves this issue.
2. Virtual Ramdisk error – The Gigastrand NVR has a virtual ramdisk where it caches images. Sometimes (especially if the motion daemon is fiddled with) the ramdisk will start writing to the user folder. Deleting the files and and NVR restart will resolve that issue as well.
3. If you have a full compliment of cameras, the default storage size of 20Gb will fill up very fast (less than 12 hours in some cases). This is too fast for the machine to effectively clean up. This issue manifests itself in the same way as the other 2 issues, but the system is essentially working.
To fix the third issue, edit the /etc/kmotion/kmotion_rc file and change the images_dbase_limit_gb to something higher than 20Gb but less than your available storage.