October 16, 201411 yr Hi, I am running the latest beta (10a) and have Cache_dirs 1.6.9 installed and invoked via the go file. To test Cache_dirs i have it running against all my shares. So far so good. The Plex docker is running fine with Cache_dirs, i can browse my collection without any disks spinning up. But the NzbDrone Docker just refreshed the TV-Series and every disk containing TV-Series spun up. It didnt write anything, just read. Isn´t that what cache_dirs should help out with?! Any idea why? Any way of preventing the disks from spinning up? Need more info? I started NzbDrone at the end of the syslog and manually spun down the disks in question.... I have my dockerfiles on an SSD mounted via SNAP. Syslog and Dockersettings attached. Syslog & Settings Pics
October 16, 201411 yr Hi, I am running the latest beta (10a) and have Cache_dirs 1.6.9 installed and invoked via the go file. To test Cache_dirs i have it running against all my shares. So far so good. The Plex docker is running fine with Cache_dirs, i can browse my collection without any disks spinning up. But the NzbDrone Docker just refreshed the TV-Series and every disk containing TV-Series spun up. It didnt write anything, just read. Isn´t that what cache_dirs should help out with?! Cache_dirs does exactly what it says, caches the directory and file listing, not the actual content of the files. I suspect NzbDrone was reading the content of some of the files, which spins up the disks.
October 16, 201411 yr Author Thanks, that makes total sense. I was an idiot and somehow thought that cache_dirs is also caching the content.....Stupid me
Archived
This topic is now archived and is closed to further replies.