Everything posted by needo
-
[Support] Linuxserver.io - Sonarr
Whenever I try to pull up the Logs it just sits and sits and sits. Thank you.
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
It is safe. I have ran this on nothing but loaded arrays.
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
Personally I have 10 disks, plus a cache drive. I am running cache_dirs with the only change being commenting out ulimit -v 5000 I have 16GB of RAM, all told all plugins (nzbget, Sickbeard, couchpotato, Plex) plus cache_dirs and I am using just over 2GB of RAM total.
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
I have. I got the same performance with lower numbers.
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
Aha! Interesting how attempting to limit cache_dirs to 5MB of virtual memory causes the errors. EDIT: It seems setting that value to any thing less then 15MB or 15360 causes things to break.
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
Word of warning: cache_dirs does not currently work on unRAID 6.0. # /boot/cache_dirs -w -i Movies -i Music -i TV ps: error while loading shared libraries: libc.so.6: failed to map segment from shared object: Cannot allocate memory sed: error while loading shared libraries: libc.so.6: failed to map segment from shared object: Cannot allocate memory sed: error while loading shared libraries: libc.so.6: failed to map segment from shared object: Cannot allocate memory sed: error while loading shared libraries: libc.so.6: failed to map segment from shared object: Cannot allocate memory sed: error while loading shared libraries: libc.so.6: failed to map segment from shared object: Cannot allocate memory /boot/cache_dirs: xmalloc: make_cmd.c:100: cannot allocate 365 bytes (98304 bytes allocated) nr_pdflush_threads exported in /proc is scheduled for removal sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case. If you have one, please send an email to [email protected].