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

Event(s) not deleted from disk when deleted in Zoneminder #748

JoelLinn opened this Issue Mar 18, 2015 · 2 comments


None yet
3 participants

JoelLinn commented Mar 18, 2015

When I use a filter to delete multiple or simply delete a single event, the event is removed from the interface only. The event folder is symlinked to a directory on a btrfs mount.
Sadly I can't do further testing on the production machine, like changing filesystem etc...

Machine is Debian 7.7 running on XenServer, ZoneMinder 1.28.0


This comment has been minimized.


knight-of-ni commented Mar 18, 2015

If OPT_FAST_DELETE is enabled under options (the default) then this is by design. You should read the help text concerning this option for a description. The zmaudit daemon will clean up orphans the next time it runs.

Also, you should not symlink the event folder. Instead, follow the instructions in the Wiki if this filesystem is on a local drive:

Naturally, adjust the parameters to match your filesystem.


This comment has been minimized.

doublehp commented Jan 12, 2017

I just ran /usr/bin/ manualy.

According to ZM web interface, the oldest event for camera 8 is 2016-dec-14 th.

According to filesystem ...

546# ls /mnt/Leon_Host_Big2/leon-03/_var_cache_zoneminder/events/8
16 17
547# ls /mnt/Leon_Host_Big2/leon-03/_var_cache_zoneminder/events/8/16/12/
08 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
548# ls /mnt/Leon_Host_Big2/leon-03/_var_cache_zoneminder/events/8/16/12/08/
549# ls /mnt/Leon_Host_Big2/leon-03/_var_cache_zoneminder/events/8/16/12/08/18/
550# ls /mnt/Leon_Host_Big2/leon-03/_var_cache_zoneminder/events/8/16/12/08/18/42/
552# ls /mnt/Leon_Host_Big2/leon-03/_var_cache_zoneminder/events/8/16/12/08/18/42/55/ | wc
615 615 11070

So I have an event for dec 8th that is out if all ZM dbs. It may never be deleted by any later script.

This is an issue for me; I have writen a script that relies on the filesystem to determine the oldest even of a camera. This kind of error by ZM will produce false resuts for me.

Several cameras have similar residues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment