Jump to content

jowe

Members
  • Content Count

    93
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jowe

  • Rank
    Advanced Member
  • Birthday 11/11/1978

Converted

  • Gender
    Male
  • Location
    Sweden
  • ICQ
    174543
  1. I have 16GB, and it's used to about 60% But i don't have anymore problems since 6.6.4 and now with 6.6.5 all cron jobs work as well JoWe
  2. Updated to unRAID 6.6.4 and problem with spinning up disks is no longer present! But it seems to use alot of CPU, around 10% with plugin disabled. And 30%+ when enabled. Changed to adaptive, and it's sleeping for 10s insted of only 1 with fixed. And the cpu is much less spiky. Thanks for your support @Alex R. Berg
  3. No problem! From what i have read, you might want to include user shares. And set cache pressure to 1. Depending on if you are having problems or not.
  4. Try using this link as @BRiT suggested. From your plugin tab, and "install plugin". https://raw.githubusercontent.com/arberg/dynamix/master/unRAIDv6/dynamix.cache.dirs.plg
  5. Hi Alex, thanks for your reply. I tried the with the new version this morning, and it has been running for a couple of hours. The disks spun down at around 7:05. After almost 2 hours. But it's still restarting a lot of times before that. Attached a file with log. I used to have a Windows HTPC with 4GB RAM, now using LibreELEC with 1GB. So I think im actually using less RAM now. And with cache pressure 0 The server "should" crash before releasing any memory. Sorry but I can't test the memory script right now, I'm not by my server so a crash would not be optimal, but i can try later tonight. I had 1.6.9 on my flash already, so i probably used that one! Started the scrip with "cache_dirs -p 1 -S -i media -u -U 0 -d 6" I'll get back with results! Edit: After running 1.6.9 for a cuple of hours, its acting exactly the same. So the problem is not from within cache_dirs. But is there anything in the newer unraid versions that could interact with cache_dirs? No times in this log, but seems to be restarting as well. This log is from when it's been running for more than 1h. Executed find in 1.630547 seconds, weighted avg=2.683402 seconds, now sleeping 10 seconds Executed find in 1.629726 seconds, weighted avg=2.332453 seconds, now sleeping 10 seconds Executed find in 1.620553 seconds, weighted avg=1.980860 seconds, now sleeping 10 seconds Executed find in 67.436761 seconds, weighted avg=7.897477 seconds, now sleeping 9 seconds Executed find in 1.629236 seconds, weighted avg=7.583565 seconds, now sleeping 10 seconds Executed find in 1.702406 seconds, weighted avg=7.276872 seconds, now sleeping 10 seconds Executed find in 1.627479 seconds, weighted avg=6.962589 seconds, now sleeping 10 seconds Executed find in 1.615260 seconds, weighted avg=6.647173 seconds, now sleeping 10 seconds Executed find in 1.600871 seconds, weighted avg=6.330583 seconds, now sleeping 10 seconds Executed find in 1.657069 seconds, weighted avg=6.019647 seconds, now sleeping 10 seconds Executed find in 1.667682 seconds, weighted avg=5.709729 seconds, now sleeping 10 seconds Executed find in 1.620685 seconds, weighted avg=5.395157 seconds, now sleeping 10 seconds Executed find in 1.629018 seconds, weighted avg=5.081718 seconds, now sleeping 10 seconds Executed find in 1.663094 seconds, weighted avg=4.771544 seconds, now sleeping 10 seconds Executed find in 1.621273 seconds, weighted avg=4.457107 seconds, now sleeping 10 seconds Executed find in 1.668013 seconds, weighted avg=4.146966 seconds, now sleeping 10 seconds Executed find in 1.666618 seconds, weighted avg=3.836455 seconds, now sleeping 10 seconds Executed find in 1.632011 seconds, weighted avg=3.522318 seconds, now sleeping 10 seconds Executed find in 1.650354 seconds, weighted avg=3.209995 seconds, now sleeping 10 seconds Executed find in 1.659944 seconds, weighted avg=2.898463 seconds, now sleeping 10 seconds Executed find in 1.621575 seconds, weighted avg=2.583238 seconds, now sleeping 10 seconds Executed find in 1.618180 seconds, weighted avg=2.267734 seconds, now sleeping 10 seconds Executed find in 1.630193 seconds, weighted avg=1.953428 seconds, now sleeping 10 seconds Executed find in 92.141068 seconds, weighted avg=10.259159 seconds, now sleeping 9 seconds Executed find in 1.648757 seconds, weighted avg=9.828936 seconds, now sleeping 10 seconds Executed find in 1.668640 seconds, weighted avg=9.400513 seconds, now sleeping 10 seconds Executed find in 1.641687 seconds, weighted avg=8.969685 seconds, now sleeping 10 seconds Executed find in 1.638518 seconds, weighted avg=8.538486 seconds, now sleeping 10 seconds Executed find in 1.601272 seconds, weighted avg=8.103630 seconds, now sleeping 10 seconds Executed find in 1.643961 seconds, weighted avg=7.672838 seconds, now sleeping 10 seconds Executed find in 1.623800 seconds, weighted avg=7.240187 seconds, now sleeping 10 seconds Executed find in 1.599030 seconds, weighted avg=6.805387 seconds, now sleeping 10 seconds Executed find in 1.657247 seconds, weighted avg=6.376234 seconds, now sleeping 10 seconds Executed find in 1.614359 seconds, weighted avg=5.942863 seconds, now sleeping 10 seconds Executed find in 1.642858 seconds, weighted avg=5.512437 seconds, now sleeping 10 seconds Executed find in 1.615809 seconds, weighted avg=5.079333 seconds, now sleeping 10 seconds Executed find in 1.608156 seconds, weighted avg=4.645748 seconds, now sleeping 10 seconds Executed find in 1.609557 seconds, weighted avg=4.212576 seconds, now sleeping 10 seconds Executed find in 1.675881 seconds, weighted avg=3.785826 seconds, now sleeping 10 seconds Executed find in 1.684113 seconds, weighted avg=3.359739 seconds, now sleeping 10 seconds Executed find in 1.550842 seconds, weighted avg=2.920845 seconds, now sleeping 10 seconds Executed find in 156.650812 seconds, weighted avg=17.253713 seconds, now sleeping 9 seconds Executed find in 170.330314 seconds, weighted avg=32.151140 seconds, now sleeping 8 seconds Executed find in 176.063238 seconds, weighted avg=46.791227 seconds, now sleeping 7 seconds Executed find in 160.003598 seconds, weighted avg=59.502194 seconds, now sleeping 6 seconds Executed find in 21.547191 seconds, weighted avg=58.272766 seconds, now sleeping 7 seconds Executed find in 1.698216 seconds, weighted avg=55.058299 seconds, now sleeping 8 seconds Executed find in 1.725258 seconds, weighted avg=51.846139 seconds, now sleeping 9 seconds Executed find in 3.315480 seconds, weighted avg=48.785016 seconds, now sleeping 10 seconds Executed find in 3.101892 seconds, weighted avg=45.695388 seconds, now sleeping 10 seconds Executed find in 1.761153 seconds, weighted avg=42.471128 seconds, now sleeping 10 seconds Executed find in 29.715485 seconds, weighted avg=41.908531 seconds, now sleeping 10 seconds Executed find in 25.123730 seconds, weighted avg=40.774737 seconds, now sleeping 10 seconds Executed find in 2.516035 seconds, weighted avg=37.376083 seconds, now sleeping 10 seconds Executed find in 1.745359 seconds, weighted avg=33.899738 seconds, now sleeping 10 seconds Executed find in 1.808898 seconds, weighted avg=30.428957 seconds, now sleeping 10 seconds Executed find in 1.869671 seconds, weighted avg=26.963043 seconds, now sleeping 10 seconds Executed find in 62.108122 seconds, weighted avg=29.232880 seconds, now sleeping 9 seconds Executed find in 9.364115 seconds, weighted avg=26.191390 seconds, now sleeping 10 seconds Executed find in 1.932508 seconds, weighted avg=22.405517 seconds, now sleeping 10 seconds cache_dirs_diagnostics.zip
  6. I'm afraid it's not working. I meant that there is no difference between now, after reinstall and before, the disks never goes to sleep while cache_dirs are running with 200K files. As i wrote in the reply below. JoWe
  7. I'm on 2.2.2 as well, i have just reinstalled and restarted the server, but after a couple of hours it seems to be no difference at all.
  8. First of all, I have been using this plugin for years, and it has been working great, there used to be more than 200K files in the share that i try to cache. Has been working until the problems with it not starting with the system. (I think) I did the same this night but increased the depth to 6 and with 200K files, the disks has not spun down a single time over the whole night. If i disable the plugin the disks spin down in 15min. JoWe cache_dirs_diagnostics.zip
  9. Yes i know that, and don't "blame" cache_dirs for thoose spin ups. JoWe
  10. Hi, I have been testing the last couple of days, and it seems that cache_dirs works, but the disks spin up much more frequent than before. I just started a windows explorer without opening any files, and it spun up 3 disks. So from what i can tell latest windows updates/versions are to blame for some of the spinning up disks. Then, there is something else as well, during this night the disks spin up, and looking at the times, some of them might be random, but most of them come at :00, :15, :30, I have tried cache_pressure 0, and the total memory consumption lies around 60% (out of 16GB). It has never hung the system. The logs are attached! It seem the disk goes to sleep much more often with the plugin disabled. Thanks JoWe 2018.11.04 23:00:02 Executed find in (40s) 40.53s, wavg=00.04s depth 3 slept 1s Disks idle before/after 532s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU= 5%, filecount[3]=431 2018.11.04 23:15:01 Executed find in (0s) 00.05s, wavg=00.04s depth 3 slept 1s Disks idle before/after 859s/859s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU=23%, filecount[3]=431 2018.11.04 23:15:02 Executed find in (0s) 00.05s, wavg=00.05s depth 3 slept 1s Disks idle before/after 1s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU=34%, filecount[3]=431 2018.11.04 23:33:36 Executed find in (0s) 00.04s, wavg=00.04s depth 3 slept 1s Disks idle before/after 9998s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU=11%, filecount[3]=431 2018.11.05 00:12:31 Executed find in (0s) 00.04s, wavg=00.04s depth 3 slept 1s Disks idle before/after 9998s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU=11%, filecount[3]=431 2018.11.05 01:00:05 Executed find in (0s) 00.06s, wavg=00.05s depth 3 slept 1s Disks idle before/after 9998s/9998s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU=41%, filecount[3]=431 2018.11.05 01:00:06 Executed find in (0s) 00.04s, wavg=00.05s depth 3 slept 1s Disks idle before/after 1s/1s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU=33%, filecount[3]=431 2018.11.05 02:00:01 Executed find in (31s) 31.08s, wavg=00.04s depth 3 slept 1s Disks idle before/after 9998s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU= 6%, filecount[3]=431 2018.11.05 02:30:01 Executed find in (8s) 08.62s, wavg=00.04s depth 3 slept 1s Disks idle before/after 9998s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU= 9%, filecount[3]=431 2018.11.05 03:15:02 Executed find in (8s) 08.70s, wavg=00.04s depth 3 slept 1s Disks idle before/after 9998s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU= 8%, filecount[3]=431 2018.11.05 04:01:52 Executed find in (0s) 00.04s, wavg=00.04s depth 3 slept 1s Disks idle before/after 9998s/9998s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU= 8%, filecount[3]=431 2018.11.05 04:01:53 Executed find in (0s) 00.04s, wavg=00.04s depth 3 slept 1s Disks idle before/after 1s/1s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU= 4%, filecount[3]=431 2018.11.05 04:15:00 Executed find in (0s) 00.04s, wavg=00.04s depth 3 slept 1s Disks idle before/after 554s/554s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU= 6%, filecount[3]=431 2018.11.05 04:15:01 Executed find in (0s) 00.11s, wavg=00.05s depth 3 slept 1s Disks idle before/after 0s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU=43%, filecount[3]=431 2018.11.05 04:30:01 Executed find in (6s) 06.80s, wavg=00.69s depth 3 slept 1s Disks idle before/after 900s/7s suc/fail cnt=0/0/0 mode=2 scan_tmo=150s maxCur=3 maxWeek=3 isMaxDepthComputed=1 CPU=15%, filecount[3]=431 cache_dirs_diagnostics.zip
  11. Hi, thanks for your reply Alex. I have tried a lot of settings, but the disks never go to sleep. Increasing timeouts adaptive/fixed and so on. Right now it's running these settings below, and if i understand the log correctly it should increase the "Disks idle before/after" But it's at 1s all the time. If I disable the plugin, the disks go to sleep as they should. With thees settings it doesn't seem to timeout at least. JoWe EDIT: "After some time it starts to increase the "Disks idle before/after" But resets the time. 2018.11.03 10:17:42 Executed find in (0s) 00.17s, wavg=00.17s depth 10 slept 1s Disks idle before/after 115s/115s suc/fail cnt=0/0/0 mode=2 scan_tmo=300s maxCur=10 maxWeek=10 isMaxDepthComputed=1 CPU=32%, filecount[10]=214712 2018.11.03 10:17:43 Executed find in (0s) 00.92s, wavg=00.24s depth 10 slept 1s Disks idle before/after 116s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=300s maxCur=10 maxWeek=10 isMaxDepthComputed=1 CPU=33%, filecount[10]=214712 2018.11.03 10:17:45 Executed find in (0s) 00.17s, wavg=00.24s depth 10 slept 1s Disks idle before/after 1s/1s suc/fail cnt=0/0/0 mode=2 scan_tmo=300s maxCur=10 maxWeek=10 isMaxDepthComputed=1 CPU=22%, filecount[10]=214712" cache_dirs version 2.2.2 Setting Memory ulimit to 100000 Setting cache_pressure=10 Arguments=-S -i media -X 300 -Y 60 -Z 120 -U 100000 -l on -D 10 Max Scan Secs=10, Min Scan Secs=1 Scan Type=fixed Max Scan Depth=10 Use Command='find -noleaf' ---------- Caching Directories --------------- media ---------------------------------------------- Setting Included dirs: media Setting Excluded dirs: min_disk_idle_before_restarting_scan_sec=60 scan_timeout_sec_idle=300 scan_timeout_sec_busy=60 scan_timeout_sec_stable=120 frequency_of_full_depth_scan_sec=604800 cache_dirs started 018.11.03 09:08:42 Executed find in (195s) 195.97s, wavg=195.97s depth 10 slept 0s Disks idle before/after 305s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=300s maxCur=10 maxWeek=10 isMaxDepthComputed=1 CPU=14%, filecount[10]=214712 2018.11.03 09:11:59 Executed find in (44s) 44.14s, wavg=195.97s depth 10 slept 1s Disks idle before/after 1s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=300s maxCur=10 maxWeek=10 isMaxDepthComputed=1 CPU=11%, filecount[10]=214712 6min later 2018.11.03 09:17:17 Executed find in (41s) 41.26s, wavg=00.16s depth 10 slept 1s Disks idle before/after 1s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=300s maxCur=10 maxWeek=10 isMaxDepthComputed=1 CPU=10%, filecount[10]=214712 2018.11.03 09:18:00 Executed find in (9s) 09.10s, wavg=00.16s depth 10 slept 1s Disks idle before/after 1s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=300s maxCur=10 maxWeek=10 isMaxDepthComputed=1 CPU=16%, filecount[10]=214712 2018.11.03 09:18:10 Executed find in (8s) 08.64s, wavg=00.16s depth 10 slept 1s Disks idle before/after 1s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=300s maxCur=10 maxWeek=10 isMaxDepthComputed=1 CPU=17%, filecount[10]=214712 2018.11.03 09:18:20 Executed find in (6s) 06.19s, wavg=00.16s depth 10 slept 1s Disks idle before/after 2s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=300s maxCur=10 maxWeek=10 isMaxDepthComputed=1 CPU=17%, filecount[10]=214712 2018.11.03 09:18:27 Executed find in (15s) 15.04s, wavg=00.16s depth 10 slept 1s Disks idle before/after 1s/0s suc/fail cnt=0/0/0 mode=2 scan_tmo=300s maxCur=10 maxWeek=10 isMaxDepthComputed=1 CPU=13%, filecount[10]=214712
  12. I'm having a problem with the plugin, the disks doesn't spin down. Have tried all latest versions, running 2.2.2 (2018.11.01-1) now. And getting this in the log file. Looks like its failing and restarting the process. Have tried multiple settings, and are running a new install with just "enable" and one included directory right now. Any ideas? 2018.10.31 19:09:59 Executed find in (0s) 00.16s, wavg=00.21s Idle____________ depth 9999 slept 10s Disks idle before/after 11s/11s suc/fail cnt=10/11/0 mode=3 scan_tmo=30s maxCur=9999 maxWeek=9999 isMaxDepthComputed=1 CPU= 9%, filecount[9999]=214446 2018.10.31 19:10:09 Executed find in (30s) 30.02s, wavg=00.21s NonIdleTooSlow__ depth 9999(timeout 30s:Error=1) slept 10s Disks idle before/after 9s/0s suc/fail cnt=11/0/1 mode=3 scan_tmo=30s maxCur=9999 maxWeek=9999 isMaxDepthComputed=1 CPU=10%, filecount[9999]=214446 2018.10.31 19:10:39 Executed find in (0s) 00.10s, wavg=00.20s Idle____________ depth 4 slept 1s Disks idle before/after 0s/0s suc/fail cnt=12/1/0 mode=3 scan_tmo=30s maxCur=5 maxWeek=9999 isMaxDepthComputed=1 CPU=66%, filecount[4]=117348
  13. Hi, I've been using LibrELEC 9 for quite some time, and now they have started the official alfa releases. It´s working quite good, but one thing has become worse since version 8. When i try to reboot or shutdown the VM from unRAID GUI, I just get the shutdown menu inside the VM. And that means i have to use the remote/keyboard to gracefully shut it down. Or Force shutdown, which is what happens when rebooting unRAID server. I tried to put a request in for an update over at LibreELEC, but just got my thread moved to "unsupported". Is there any way to do this from unRIAD? JoWe
  14. jowe

    IGD Device Assignment to VMs

    That's nice! I use 2 vcpu, i440fx-2.7 and 2GB of RAM. Another thing i thought about. Do you change your frame-rate to reflect the frame-rate of the video you are playing. I think it was working better with that of, but that can make the video lag in big panoramic scenes. Anyway, glad its working, but you shouldn't need all 4 cores for Libre/Open-ELEC. JoWe
  15. jowe

    IGD Device Assignment to VMs

    Hi, I have the same audio device in unraid. And I still have this problem also, once every 10th start of a movie or so, but a stop and restart of movie fixes that. Sometimes i had to do a reboot of that VM to make it work, but since i scheduled a restart of VM over night , the problem is not really an issue. I have an install of LibreELEC 8 done with this guide