9 minutes ago, dlandon said:

Both servers are the same setup.  Cache is an SSD and system share is on cache as 'Prefer' cache setting.  Why would there be a difference?

 

Both systems have the same plugin version?

 

The schedule which is used to trim all available sources (see /etc/cron.d/root) looks like:

# Generated ssd trim schedule:
25 6 * * * /sbin/fstrim -a -v | logger &> /dev/null

 

1 hour ago, nuhll said:

Hey, i use the cache thingy, but doesnt seem to work correct.

 

I added /Archiv/ and /downloads/

 

If i visit /Archiv/ a drive spinns up...

 

Did you add these shares to the include/exclude settings of the plugin?

When you add new shares you'll need to restart or reconfigure the plugin to let it learn these new shares.

Like i said, i added Archiv and downloads (but downloads is on cache ssd anyway)

Archiv is the array, and its added. Still disks spin up, just when i visit the folder.

If u change config, it reloads automatic, it seems like.

 

Edited December 30, 20178 yr by nuhll

What is the output of

ps -ef | grep cache.dirs

 

13 minutes ago, bonienl said:

 

Both systems have the same plugin version?

 

The schedule which is used to trim all available sources (see /etc/cron.d/root) looks like:

# Generated ssd trim schedule:
25 6 * * * /sbin/fstrim -a -v | logger &> /dev/null

 

This is the cron on my server:

# Generated ssd trim schedule:
30 5 * * * /sbin/fstrim -v /mnt/cache | logger &> /dev/null

Both servers running 2017.04.23a.  Ok.  I figured out one difference that could affect the decision to include the '-a'.  On my backup server I have a UD ssd and that is probably what is used to include the '-a'.

9 minutes ago, dlandon said:

Both servers running 2017.04.23a

 

Re-apply the trim settings on your main server, it should get the "-a" added.

5 minutes ago, bonienl said:

 

Re-apply the trim settings on your main server, it should get the "-a" added.

That got it.  Thank you.

root@Unraid-Server:~# ps -ef | grep cache.dirs
root       374     1  0 12:50 ?        00:00:15 /bin/bash /usr/local/emhttp/plugins/dynamix.cache.dirs/scripts/cache_dirs -u -e http_cache -i Archiv -i downloads
root      9381  9296  0 15:22 pts/0    00:00:00 grep cache.dirs

 

 

This time no hdd spined up.

 

I will go now, and when i come back check again if it works now, if not, i come back and report.
 

Edited December 30, 20178 yr by nuhll

Use only "include" or only "exclude" but not both. When you fill-in for example the "include" list then automatically all others are excluded.

8 hours ago, John_M said:

 

On page 69: this reply.

 

Tip: You can search within the current topic using the search box at the top right corner of the page.

 

Thanks John_M learned something new every day. I'll wait for the update then.

So i removed the include and just put an exclude in. Yesterday it worked, now it wont work...i dont get it.

 

root@Unraid-Server:/# ps -ef | grep cache.dirs
root      5974     1  0 Dec30 ?        00:01:10 /bin/bash /usr/local/emhttp/plugins/dynamix.cache.dirs/scripts/cache_dirs -u -e http_cache
root     15167 15096  0 11:56 pts/2    00:00:00 grep cache.dirs

 

23 hours ago, nuhll said:

Still disks spin up, just when i visit the folder.

What exactly do you mean by "visit"?  Some file browsers may try to load additional information about files, such as icons. Those are not cached and so must be read from the disk.

SMB, just clicking the shortcut. Now i tried again - didnt changed anything - and disks didnt spin up.

 

Does he delete cache? Btw, where is the cache stored?

Edited December 31, 20178 yr by nuhll

4 minutes ago, nuhll said:

SMB, just clicking the shortcut. Now i tried again - didnt changed anything - and disks didnt spin up.

 

Does he delete cache? Btw, where is the cache stored?

 

In memory. 

The Directory Cache is in RAM used by the Linux kernel. Nothing permanent is stored anywhere with Cache Dirs program -- all it does is continually do directory listings so the Kernel keeps using the entries so they're still in use and less likely to be purged from it's cache.

 

Thats good.  Does cache gets deleted? So its normal a few times a gday disks spinning up?

Edited December 31, 20178 yr by nuhll

I have just installed System Temp and Fan Auto Control in my Server, running on a Supermicro X11SSM-F motherboard.

System Temp works without installing perl.

Problem is I don't see any PWM controller in Fan Auto Control. I read through most of the thread but can't find any solution.

Please help.

27 minutes ago, Miles- said:

X11SSM-F

For that board I recommend you install the IPMI plugin for fan control

3 hours ago, johnnie.black said:

For that board I recommend you install the IPMI plugin for fan control

Thank you

Okay, it seems like the drive is from time to time spinning up, atleast once a day, i dont get why. While its better then without, i guess no spinning up would be the best, how long the cache stays valid?

On 04/01/2018 at 12:53 PM, nuhll said:

how long the cache stays valid?

 

Until some other process needs the memory. I don't think it's possible to be more specific than that. If you have plenty of memory and not much demand for it and a relatively small number of files the chances are the directory information will stay cached for a long time. If you have some process that needs a lot of memory running, say, once a day then the cache may end up being purged every day so that the memory can be re-allocated by the kernel.

After installing the temp plugin and PERL I was able to locate a coretemp driver by detection and then see sensors/temps, but I never really set and saved them.

 

I came back later it doesn't show anything under the sensors/temps, the driver shows but that's it.

The command line also shows the following error over and over until I go delete the plugin.

 

sensors_init: Can't parse bus name

Edited January 12, 20188 yr by CorneliousJD

Perhaps the video of gridrunner can help you out.

 

1 minute ago, bonienl said:

Perhaps the video of gridrunner can help you out.

 

That's actually what I watched that made me go get the plugin

I have a problem with S3 sleep plugin, it's putting my server to sleep after the defined period, regardless of array activity (eg. when I'm watching a movie). I have set the "Wait for array inactivity" to "Yes, exclude Cache" and in the syslog I see the following:

Jan 14 11:18:23 StatekMatka s3_sleep: action mode=sleep
Jan 14 11:18:23 StatekMatka s3_sleep: check disks status=yes
Jan 14 11:18:23 StatekMatka s3_sleep: check network activity=no
Jan 14 11:18:23 StatekMatka s3_sleep: check active devices=no
Jan 14 11:18:23 StatekMatka s3_sleep: check local login=no
Jan 14 11:18:23 StatekMatka s3_sleep: check remote login=no
Jan 14 11:18:23 StatekMatka s3_sleep: version=3.0.4
Jan 14 11:18:23 StatekMatka s3_sleep: ----------------------------------------------
Jan 14 11:18:23 StatekMatka s3_sleep: included disks=
Jan 14 11:18:23 StatekMatka s3_sleep: excluded disks=sda sdb sdc sdd sde sdf

where sde is my Cache disk. When I set "Wait for array inactivity" to just "Yes", what I get in syslog is:

Jan 14 11:23:16 StatekMatka s3_sleep: action mode=sleep
Jan 14 11:23:16 StatekMatka s3_sleep: check disks status=yes
Jan 14 11:23:16 StatekMatka s3_sleep: check network activity=no
Jan 14 11:23:16 StatekMatka s3_sleep: check active devices=no
Jan 14 11:23:16 StatekMatka s3_sleep: check local login=no
Jan 14 11:23:16 StatekMatka s3_sleep: check remote login=no
Jan 14 11:23:16 StatekMatka s3_sleep: version=3.0.4
Jan 14 11:23:16 StatekMatka s3_sleep: ----------------------------------------------
Jan 14 11:23:16 StatekMatka s3_sleep: included disks=sde
Jan 14 11:23:16 StatekMatka s3_sleep: excluded disks=sda sdb sdc sdd sdf

Is this correct?

statekmatka-diagnostics-20180114-1133.zip