0.8.8-beta-docker: stale folders not removed with Local library scan

csammis

I'm receiving thousands of FileNotFound warnings in my ETV logs on a daily basis, and I figured out that it's because some of the folders which were present when the local library was created have been deleted from the disk. Problem is that scanning the library in ETV (using the 'Refresh' button in the 'Libraries' UI) does not remove the folders from that library. They still show up when browsing the library from the ETV web UI and still show up in a search. I've connected to the docker container and confirmed that the folders aren't mysteriously still there on its mounted volume.

The library scan does find newly added folders.

This issue was also present on 0.8.7-beta-docker.

How can I remove the missing folders from the ETV library so that I can clean up the logs?

csammis

To clear up any potential ambiguity: the Local library has one single library path, which is the mount point for the docker volume mapping to the root of my NAS's media storage. It's folders underneath that path which aren't being removed from the ETV database at scan time.

jason

You can empty the trash to remove items that you want ETV to forget about.

csammis

Ack, that took care of it, thanks!