Squid

But it automatically starts back up again on a reboot if there are users defined, (and even if there are not, the service is still running). Personally, I want the ability to disable all unused services period.

Because your trying to map a file instead of a folder which contains the file. I didn't check the cut and paste I did. [emoji33] Sent from my LG-D852 using Tapatalk

then can someone convert this so i can manage it through the docker tab? Turn on dockerhub searches within CA settings, then search for dvdgiessen. You'll have to add the port of 1935, and a volume mapping of /path/to/my/custom/nginx.conf mapped to /etc/nginx/nginx.conf (its not an automated build, so CA won't be able to populate those fields)

dunno. If you're still using the same two paths, you would think it would be slower since you're going over the network and it still has to read, write, delete. But, if you had the paths in winscp to use the same mount points, then its damn near instantaneous since all it has to do is a rename.

This shouldn't matter because with the --cpuset it should not allow the container to use more than two cores of the CPU. Agree Don't particularly pay that much attention to it. But I can tell you that the --cpuset-cpus does work. I test it with Folding@home You'd really have to look at running htop or something so you can see exactly what the top processes are and where they are from.

This is the key right there ^^^ Those are two different mount points (NCmisc, and media), so any OS (not just unRaid) has to do a read, write, delete process to move the file, and ~50MB/s writing to a user share is about right (depending upon useCache settings, etc) (Note that I don't actually use FileBot, but from what your saying, the above is correct) You can on 6.2RC3+

Yes. (Since that section in disk settings doesn't have a "default" button, just clearing the entries and then hitting apply will set them to (and display) the default values

Doing anything like that over the network is going to be significantly slower than locally on the server itself (ie: Krusader), simply because of the amount of back and forth traffic via the network. And not all NICs properly support full duplex transmissions either (my Realtek NICs significantly drop the transfer speed if they are sending / receiving simultaneously and in theory, full duplex means that they shouldn't)

I know, but the SCSI devices plugin may just be a temporary fix. It is under discussion at the moment. I consider it my job to harp on people around here Ok, you forced gently pushed me to add "dynamix date time" as a new entry And don't you have the warm, fuzzy feeling knowing that the job has been completed?

I know, but the SCSI devices plugin may just be a temporary fix. It is under discussion at the moment. I consider it my job to harp on people around here

One day you'll have to get around to creating the two new xml files (and you can use the <MinVer> tag on them)

It could also be shfs (unraid) spiking the cpu to actually rw the files. Sent from my LG-D852 using Tapatalk

What does cAdvisor show for the App? You can install it via CA resource monitor. It works for me exactly how you have it listed. Also by 4 cores do you mean 2 hyperthreaded cores? Sent from my SM-T560NU using Tapatalk

Rings a bell. Can't quite remember however. Have you checked (and installed) all available plugin updates and dynamix webUI updates?

Same here. Same here too. DOH! PM eschultz and limetech

Same here.

Extensions changed to .txt CSV_ServerA.txt CSV_ServerB.txt

You should remove Preclear Beta from your system. The new script has been integrated in the normal Preclear Script plugin. So I don't have to install the seperate preclear script with the normal preclear plugin anymore? If so, you should update the description on the xml (for CA). And remove the xml for the beta version. Don't suppose there's much reason to have a plg for CA that does absolutely nothing. (Additionally, update the image within the .xml since it doesn't work anymore either)

Server B unRAID Tunables Tester v4.0b3 by Pauven (for unRAID v6.2) Tunables Report produced Fri Aug 26 08:15:57 EDT 2016 Run on server: Server_B Normal Automatic Parity Sync Test Current Values: md_num_stripes=1280, md_sync_window=384, md_sync_thresh=192 Global nr_requests=128 sdd nr_requests=128 sdf nr_requests=128 sdb nr_requests=128 sdc nr_requests=128 sde nr_requests=128 sdg nr_requests=128 sdl nr_requests=128 sdh nr_requests=128 sdi nr_requests=128 sdj nr_requests=128 sdk nr_requests=128 sdm nr_requests=128 --- INITIAL BASELINE TEST OF CURRENT VALUES (1 Sample Point @ 5min Duration)--- Test | RAM | stripes | window | reqs | thresh | MB/s ------------------------------------------------------- 1 | 68 | 1280 | 384 | 128 | 192 | 59.3 --- FULLY AUTOMATIC nr_requests TEST 1 (4 Sample Points @ 10min Duration)--- Test | num_stripes | sync_window | nr_requests | sync_thresh | Speed --------------------------------------------------------------------------- 1 | 1536 | 768 | 128 | 767 | 95.3 MB/s 2 | 1536 | 768 | 128 | 384 | 80.5 MB/s 3 | 1536 | 768 | 8 | 767 | 95.9 MB/s 4 | 1536 | 768 | 8 | 384 | 80.1 MB/s Fastest vals were nr_reqs=8 and sync_thresh=99% of sync_window at 95.9 MB/s This nr_requests value will be used for the next test. --- FULLY AUTOMATIC TEST PASS 1a (Rough - 13 Sample Points @ 5min Duration)--- Test | RAM | stripes | window | reqs | thresh | MB/s | thresh | MB/s ------------------------------------------------------------------------ 1 | 40 | 768 | 384 | 8 | 383 | 82.5 | 192 | 61.3 2 | 47 | 896 | 448 | 8 | 447 | 91.0 | 224 | 63.2 3 | 54 | 1024 | 512 | 8 | 511 | 90.2 | 256 | 66.0 4 | 61 | 1152 | 576 | 8 | 575 | 97.7 | 288 | 65.7 5 | 68 | 1280 | 640 | 8 | 639 | 98.8 | 320 | 67.0 6 | 75 | 1408 | 704 | 8 | 703 | 100.0 | 352 | 68.0 7 | 81 | 1536 | 768 | 8 | 767 | 98.3 | 384 | 69.6 8 | 88 | 1664 | 832 | 8 | 831 | 98.5 | 416 | 69.9 9 | 95 | 1792 | 896 | 8 | 895 | 99.6 | 448 | 70.8 10 | 102 | 1920 | 960 | 8 | 959 | 93.0 | 480 | 72.1 11 | 109 | 2048 | 1024 | 8 | 1023 | 96.1 | 512 | 72.9 12 | 115 | 2176 | 1088 | 8 | 1087 | 102.0 | 544 | 78.4 13 | 122 | 2304 | 1152 | 8 | 1151 | 101.4 | 576 | 81.7 --- FULLY AUTOMATIC TEST PASS 1c (Rough - 17 Sample Points @ 5min Duration)--- Test | RAM | stripes | window | reqs | thresh | MB/s | thresh | MB/s ------------------------------------------------------------------------ 1 | 129 | 2432 | 1216 | 8 | 1215 | 105.0 | 608 | 84.5 2 | 136 | 2560 | 1280 | 8 | 1279 | 102.3 | 640 | 98.7 3 | 143 | 2688 | 1344 | 8 | 1343 | 102.7 | 672 | 103.5 4 | 150 | 2816 | 1408 | 8 | 1407 | 103.0 | 704 | 102.2 5 | 156 | 2944 | 1472 | 8 | 1471 | 102.5 | 736 | 104.9 6 | 163 | 3072 | 1536 | 8 | 1535 | 103.2 | 768 | 100.6 7 | 170 | 3200 | 1600 | 8 | 1599 | 101.7 | 800 | 102.7 8 | 177 | 3328 | 1664 | 8 | 1663 | 102.5 | 832 | 105.0 9 | 184 | 3456 | 1728 | 8 | 1727 | 105.8 | 864 | 101.1 10 | 191 | 3584 | 1792 | 8 | 1791 | 100.3 | 896 | 103.7 11 | 197 | 3712 | 1856 | 8 | 1855 | 99.7 | 928 | 89.4 12 | 204 | 3840 | 1920 | 8 | 1919 | 91.0 | 960 | 95.8 13 | 211 | 3968 | 1984 | 8 | 1983 | 100.4 | 992 | 101.9 14 | 218 | 4096 | 2048 | 8 | 2047 | 99.0 | 1024 | 89.7 15 | 225 | 4224 | 2112 | 8 | 2111 | 90.4 | 1056 | 88.2 16 | 231 | 4352 | 2176 | 8 | 2175 | 90.1 | 1088 | 93.1 17 | 238 | 4480 | 2240 | 8 | 2239 | 95.9 | 1120 | 95.7 --- Targeting Fastest Result of md_sync_window 1728 bytes for Final Pass --- --- FULLY AUTOMATIC nr_requests TEST 2 (4 Sample Points @ 10min Duration)--- Test | num_stripes | sync_window | nr_requests | sync_thresh | Speed --------------------------------------------------------------------------- 1 | 3456 | 1728 | 128 | 1727 | 93.9 MB/s 2 | 3456 | 1728 | 128 | 864 | 81.0 MB/s 3 | 3456 | 1728 | 8 | 1727 | 75.2 MB/s 4 | 3456 | 1728 | 8 | 864 | 73.9 MB/s Fastest vals were nr_reqs=128 and sync_thresh=99% of sync_window at 93.9 MB/s This nr_requests value will be used for the next test. --- FULLY AUTOMATIC TEST PASS 2 (Fine - 33 Sample Points @ 5min Duration)--- Test | RAM | stripes | window | reqs | thresh | MB/s | thresh | MB/s ------------------------------------------------------------------------ 1 | 170 | 3200 | 1600 | 128 | 1599 | 78.3 | 800 | 74.5 2 | 171 | 3216 | 1608 | 128 | 1607 | 79.2 | 804 | 83.6 3 | 172 | 3232 | 1616 | 128 | 1615 | 82.3 | 808 | 81.7 4 | 173 | 3248 | 1624 | 128 | 1623 | 77.0 | 812 | 80.3 5 | 173 | 3264 | 1632 | 128 | 1631 | 82.4 | 816 | 84.0 6 | 174 | 3280 | 1640 | 128 | 1639 | 81.4 | 820 | 88.6 7 | 175 | 3296 | 1648 | 128 | 1647 | 90.3 | 824 | 87.9 8 | 176 | 3312 | 1656 | 128 | 1655 | 88.6 | 828 | 84.7 9 | 177 | 3328 | 1664 | 128 | 1663 | 85.4 | 832 | 81.5 10 | 178 | 3344 | 1672 | 128 | 1671 | 84.7 | 836 | 86.3 11 | 179 | 3360 | 1680 | 128 | 1679 | 88.9 | 840 | 87.5 12 | 179 | 3376 | 1688 | 128 | 1687 | 90.3 | 844 | 92.6 13 | 180 | 3392 | 1696 | 128 | 1695 | 84.5 | 848 | 79.9 14 | 181 | 3408 | 1704 | 128 | 1703 | 77.5 | 852 | 77.2 15 | 182 | 3424 | 1712 | 128 | 1711 | 80.0 | 856 | 74.6 16 | 183 | 3440 | 1720 | 128 | 1719 | 79.2 | 860 | 82.5 17 | 184 | 3456 | 1728 | 128 | 1727 | 81.5 | 864 | 86.1 18 | 185 | 3472 | 1736 | 128 | 1735 | 70.1 | 868 | 77.3 19 | 185 | 3488 | 1744 | 128 | 1743 | 79.8 | 872 | 76.7 20 | 186 | 3504 | 1752 | 128 | 1751 | 76.3 | 876 | 80.9 21 | 187 | 3520 | 1760 | 128 | 1759 | 75.4 | 880 | 80.0 22 | 188 | 3536 | 1768 | 128 | 1767 | 91.5 | 884 | 77.6 23 | 189 | 3552 | 1776 | 128 | 1775 | 65.5 | 888 | 67.9 24 | 190 | 3568 | 1784 | 128 | 1783 | 73.6 | 892 | 73.0 25 | 191 | 3584 | 1792 | 128 | 1791 | 72.3 | 896 | 81.2 26 | 191 | 3600 | 1800 | 128 | 1799 | 89.8 | 900 | 94.0 27 | 192 | 3616 | 1808 | 128 | 1807 | 92.5 | 904 | 85.3 28 | 193 | 3632 | 1816 | 128 | 1815 | 81.9 | 908 | 75.4 29 | 194 | 3648 | 1824 | 128 | 1823 | 73.6 | 912 | 82.1 30 | 195 | 3664 | 1832 | 128 | 1831 | 80.1 | 916 | 79.1 31 | 196 | 3680 | 1840 | 128 | 1839 | 84.5 | 920 | 90.9 32 | 196 | 3696 | 1848 | 128 | 1847 | 79.2 | 924 | 80.0 33 | 197 | 3712 | 1856 | 128 | 1855 | 76.7 | 928 | 74.1 The results below do NOT include the Basline test of current values. The Fastest Sync Speed tested was md_sync_window=1216 at 105.0 MB/s Tunable (md_num_stripes): 2432 Tunable (md_sync_window): 1216 Tunable (md_sync_thresh): 1215 Tunable (nr_requests): 128 This will consume 129 MB with md_num_stripes=2432, 2x md_sync_window. This is 61MB more than your current utilization of 68MB. The Thriftiest Sync Speed tested was md_sync_window=704 at 100.0 MB/s Tunable (md_num_stripes): 1408 Tunable (md_sync_window): 704 Tunable (md_sync_thresh): 703 Tunable (nr_requests): 128 This will consume 75 MB with md_num_stripes=1408, 2x md_sync_window. This is 7MB more than your current utilization of 68MB. The Recommended Sync Speed is md_sync_window=1216 at 105.0 MB/s Tunable (md_num_stripes): 2432 Tunable (md_sync_window): 1216 Tunable (md_sync_thresh): 1215 Tunable (nr_requests): 128 This will consume 129 MB with md_num_stripes=2432, 2x md_sync_window. This is 61MB more than your current utilization of 68MB. NOTE: Adding additional drives will increase memory consumption. In unRAID, go to Settings > Disk Settings to set your chosen parameter values. Completed: 12 Hrs 44 Min 2 Sec. NOTE: Use the smallest set of values that produce good results. Larger values increase server memory use, and may cause stability issues with unRAID, especially if you have any add-ons or plug-ins installed. System Info: Server_B unRAID version 6.2.0-rc4 md_num_stripes=1280 md_sync_window=384 md_sync_thresh=192 nr_requests=128 (Global Setting) sbNumDisks=13 CPU: AMD Sempron(tm) 3850 APU with Radeon(tm) R3 91xx Config RAM: 4GiB System Memory Outputting lshw information for Drives and Controllers: H/W path Device Class Description ======================================================== /0/100/2.1/0 scsi11 storage SAS1068E PCI-Express Fusion-MPT SAS /0/100/2.1/0/0.4.0 /dev/sdj disk 1TB ST31000333AS /0/100/2.1/0/0.5.0 /dev/sdk disk 2TB Hitachi HDS72202 /0/100/2.1/0/0.6.0 /dev/sdl disk 2TB WDC WD20EFRX-68E /0/100/2.1/0/0.7.0 /dev/sdm disk 1TB ST31000528AS /0/100/2.1/0/0.0.0 /dev/sdf disk 2TB ST2000DM001-1CH1 /0/100/2.1/0/0.1.0 /dev/sdg disk 2TB ST2000DM001-1CH1 /0/100/2.1/0/0.2.0 /dev/sdh disk 1TB Hitachi HDT72101 /0/100/2.1/0/0.3.0 /dev/sdi disk 1TB ST31000524AS /0/100/2.2/0 storage 88SE9123 PCIe SATA 6.0 Gb/s controller /0/100/11 storage FCH SATA Controller [AHCI mode] /0/1 scsi0 storage /0/1/0.0.0 /dev/sda disk 31GB USB Flash Drive /0/1/0.0.0/0 /dev/sda disk 31GB /0/2 scsi1 storage /0/2/0.0.0 /dev/sdb disk 2TB ST2000DM001-1CH1 /0/2/0.0.0/0 /dev/sdb disk 2TB /0/3 scsi2 storage /0/3/0.0.0 /dev/sdc disk 3TB ST3000DM001-1CH1 /0/3/0.0.0/0 /dev/sdc disk 3TB /0/4 scsi3 storage /0/4/0.0.0 /dev/sdd disk 3TB ST3000DM001-1CH1 /0/5 scsi4 storage /0/5/0.0.0 /dev/sde disk 2TB ST2000DL003-9VT1 /0/6 scsi10 storage Array Devices: Disk0 sdd is a Parity drive named parity Disk1 sdf is a Data drive named disk1 Disk2 sdb is a Data drive named disk2 Disk3 sdc is a Data drive named disk3 Disk4 sde is a Data drive named disk4 Disk5 sdg is a Data drive named disk5 Disk6 sdl is a Data drive named disk6 Disk7 sdh is a Data drive named disk7 Disk8 sdi is a Data drive named disk8 Disk9 sdj is a Data drive named disk9 Disk10 sdk is a Data drive named disk10 Disk11 sdm is a Data drive named disk11 Outputting free low memory information... total used free shared buff/cache available Mem: 3961340 177772 3042704 649288 740864 2904704 Low: 3961340 918636 3042704 High: 0 0 0 Swap: 0 0 0 *** END OF REPORT ***

My normal test results: Server_A unRAID Tunables Tester v4.0b3 by Pauven (for unRAID v6.2) Tunables Report produced Fri Aug 26 08:47:57 EDT 2016 Run on server: Server_A Normal Automatic Parity Sync Test Current Values: md_num_stripes=1280, md_sync_window=384, md_sync_thresh=192 Global nr_requests=128 sdg nr_requests=128 sdl nr_requests=128 sdc nr_requests=128 sde nr_requests=128 sdf nr_requests=128 sdh nr_requests=128 sdk nr_requests=128 sdi nr_requests=128 sdm nr_requests=128 sdj nr_requests=128 sdd nr_requests=128 --- INITIAL BASELINE TEST OF CURRENT VALUES (1 Sample Point @ 5min Duration)--- Test | RAM | stripes | window | reqs | thresh | MB/s ------------------------------------------------------- 1 | 63 | 1280 | 384 | 128 | 192 | 99.5 --- FULLY AUTOMATIC nr_requests TEST 1 (4 Sample Points @ 10min Duration)--- Test | num_stripes | sync_window | nr_requests | sync_thresh | Speed --------------------------------------------------------------------------- 1 | 1536 | 768 | 128 | 767 | 74.2 MB/s 2 | 1536 | 768 | 128 | 384 | 112.6 MB/s 3 | 1536 | 768 | 8 | 767 | 111.7 MB/s 4 | 1536 | 768 | 8 | 384 | 111.7 MB/s Fastest vals were nr_reqs=128 and sync_thresh=50% of sync_window at 112.6 MB/s This nr_requests value will be used for the next test. --- FULLY AUTOMATIC TEST PASS 1a (Rough - 13 Sample Points @ 5min Duration)--- Test | RAM | stripes | window | reqs | thresh | MB/s | thresh | MB/s ------------------------------------------------------------------------ 1 | 37 | 768 | 384 | 128 | 383 | 48.5 | 192 | 106.4 2 | 44 | 896 | 448 | 128 | 447 | 53.0 | 224 | 103.1 3 | 50 | 1024 | 512 | 128 | 511 | 59.9 | 256 | 102.2 4 | 56 | 1152 | 576 | 128 | 575 | 64.2 | 288 | 102.3 5 | 63 | 1280 | 640 | 128 | 639 | 70.4 | 320 | 98.7 6 | 69 | 1408 | 704 | 128 | 703 | 74.4 | 352 | 98.8 7 | 75 | 1536 | 768 | 128 | 767 | 77.4 | 384 | 99.5 8 | 82 | 1664 | 832 | 128 | 831 | 81.3 | 416 | 100.9 9 | 88 | 1792 | 896 | 128 | 895 | 84.6 | 448 | 100.3 10 | 94 | 1920 | 960 | 128 | 959 | 87.7 | 480 | 102.8 11 | 101 | 2048 | 1024 | 128 | 1023 | 88.0 | 512 | 104.5 12 | 107 | 2176 | 1088 | 128 | 1087 | 92.8 | 544 | 105.7 13 | 113 | 2304 | 1152 | 128 | 1151 | 94.4 | 576 | 105.1 --- FULLY AUTOMATIC TEST PASS 1b (Rough - 5 Sample Points @ 5min Duration)--- Test | RAM | stripes | window | reqs | thresh | MB/s | thresh | MB/s ------------------------------------------------------------------------ 1 | 6 | 128 | 64 | 128 | 63 | 12.0 | 32 | 111.7 2 | 12 | 256 | 128 | 128 | 127 | 21.7 | 64 | 115.9 3 | 18 | 384 | 192 | 128 | 191 | 29.2 | 96 | 114.6 4 | 25 | 512 | 256 | 128 | 255 | 36.2 | 128 | 107.5 5 | 31 | 640 | 320 | 128 | 319 | 43.8 | 160 | 107.7 --- Targeting Fastest Result of md_sync_window 128 bytes for Final Pass --- --- FULLY AUTOMATIC nr_requests TEST 2 (4 Sample Points @ 10min Duration)--- Test | num_stripes | sync_window | nr_requests | sync_thresh | Speed --------------------------------------------------------------------------- 1 | 256 | 128 | 128 | 127 | 21.3 MB/s 2 | 256 | 128 | 128 | 64 | 113.8 MB/s 3 | 256 | 128 | 8 | 127 | 66.8 MB/s 4 | 256 | 128 | 8 | 64 | 116.1 MB/s Fastest vals were nr_reqs=8 and sync_thresh=50% of sync_window at 116.1 MB/s This nr_requests value will be used for the next test. --- FULLY AUTOMATIC TEST PASS 2 (Fine - 33 Sample Points @ 5min Duration)--- Test | RAM | stripes | window | reqs | thresh | MB/s | thresh | MB/s ------------------------------------------------------------------------ 1 | 0 | 16 | 8 | 8 | 7 | 6.5 | 4 | 30.5 2 | 1 | 32 | 16 | 8 | 15 | 12.2 | 8 | 60.4 3 | 2 | 48 | 24 | 8 | 23 | 17.0 | 12 | 75.2 4 | 3 | 64 | 32 | 8 | 31 | 22.7 | 16 | 85.6 5 | 3 | 80 | 40 | 8 | 39 | 27.8 | 20 | 94.0 6 | 4 | 96 | 48 | 8 | 47 | 31.3 | 24 | 91.7 7 | 5 | 112 | 56 | 8 | 55 | 35.7 | 28 | 99.6 8 | 6 | 128 | 64 | 8 | 63 | 37.2 | 32 | 101.0 9 | 7 | 144 | 72 | 8 | 71 | 40.3 | 36 | 101.5 10 | 7 | 160 | 80 | 8 | 79 | 41.6 | 40 | 97.6 11 | 8 | 176 | 88 | 8 | 87 | 44.6 | 44 | 95.9 12 | 9 | 192 | 96 | 8 | 95 | 48.6 | 48 | 103.3 13 | 10 | 208 | 104 | 8 | 103 | 50.6 | 52 | 104.2 14 | 11 | 224 | 112 | 8 | 111 | 53.7 | 56 | 99.0 15 | 11 | 240 | 120 | 8 | 119 | 56.7 | 60 | 106.3 16 | 12 | 256 | 128 | 8 | 127 | 59.2 | 64 | 100.0 17 | 13 | 272 | 136 | 8 | 135 | 61.4 | 68 | 94.7 18 | 14 | 288 | 144 | 8 | 143 | 62.0 | 72 | 93.8 19 | 15 | 304 | 152 | 8 | 151 | 64.5 | 76 | 99.7 20 | 15 | 320 | 160 | 8 | 159 | 68.1 | 80 | 98.8 21 | 16 | 336 | 168 | 8 | 167 | 68.9 | 84 | 100.8 22 | 17 | 352 | 176 | 8 | 175 | 70.8 | 88 | 100.0 23 | 18 | 368 | 184 | 8 | 183 | 73.6 | 92 | 103.6 24 | 18 | 384 | 192 | 8 | 191 | 77.6 | 96 | 100.2 25 | 19 | 400 | 200 | 8 | 199 | 77.8 | 100 | 105.1 26 | 20 | 416 | 208 | 8 | 207 | 77.0 | 104 | 99.7 27 | 21 | 432 | 216 | 8 | 215 | 79.8 | 108 | 104.9 28 | 22 | 448 | 224 | 8 | 223 | 80.3 | 112 | 100.3 29 | 22 | 464 | 232 | 8 | 231 | 81.6 | 116 | 99.6 30 | 23 | 480 | 240 | 8 | 239 | 81.4 | 120 | 94.0 31 | 24 | 496 | 248 | 8 | 247 | 85.5 | 124 | 104.1 32 | 25 | 512 | 256 | 8 | 255 | 86.5 | 128 | 98.5 The results below do NOT include the Basline test of current values. The Fastest Sync Speed tested was md_sync_window=320 at 107.7 MB/s Tunable (md_num_stripes): 640 Tunable (md_sync_window): 320 Tunable (md_sync_thresh): 160 Tunable (nr_requests): 8 This will consume 31 MB with md_num_stripes=640, 2x md_sync_window. This is 32MB less than your current utilization of 63MB. The Thriftiest Sync Speed tested was md_sync_window=96 at 103.3 MB/s Tunable (md_num_stripes): 192 Tunable (md_sync_window): 96 Tunable (md_sync_thresh): 48 Tunable (nr_requests): 8 This will consume 9 MB with md_num_stripes=192, 2x md_sync_window. This is 54MB less than your current utilization of 63MB. The Recommended Sync Speed is md_sync_window=320 at 107.7 MB/s Tunable (md_num_stripes): 640 Tunable (md_sync_window): 320 Tunable (md_sync_thresh): 160 Tunable (nr_requests): 8 This will consume 31 MB with md_num_stripes=640, 2x md_sync_window. This is 32MB less than your current utilization of 63MB. NOTE: Adding additional drives will increase memory consumption. In unRAID, go to Settings > Disk Settings to set your chosen parameter values. Completed: 11 Hrs 30 Min 46 Sec. NOTE: Use the smallest set of values that produce good results. Larger values increase server memory use, and may cause stability issues with unRAID, especially if you have any add-ons or plug-ins installed. System Info: Server_A unRAID version 6.2.0-rc4 md_num_stripes=1280 md_sync_window=384 md_sync_thresh=192 nr_requests=128 (Global Setting) sbNumDisks=12 CPU: AMD A8-6600K APU with Radeon(tm) HD Graphics RAM: 12GiB System Memory Outputting lshw information for Drives and Controllers: H/W path Device Class Description ======================================================== /0/100/3/0 scsi5 storage 88SE9485 SAS/SATA 6Gb/s controller /0/100/3/0/0.5.0 /dev/sdk disk 4TB ST4000DM000-1F21 /0/100/3/0/0.6.0 /dev/sdl disk 3TB ST3000DM001-1CH1 /0/100/3/0/0.7.0 /dev/sdm disk 3TB ST3000DM001-9YN1 /0/100/3/0/0.0.0 /dev/sdf disk 3TB ST3000DM001-1CH1 /0/100/3/0/0.1.0 /dev/sdg disk 4TB ST4000DM000-1F21 /0/100/3/0/0.2.0 /dev/sdh disk 3TB ST3000DM001-1CH1 /0/100/3/0/0.3.0 /dev/sdi disk 3TB ST3000DM001-1CH1 /0/100/3/0/0.4.0 /dev/sdj disk 3TB ST3000DM001-1ER1 /0/100/11 storage FCH SATA Controller [AHCI mode] /0/1 scsi0 storage /0/1/0.0.0 /dev/sda disk 7756MB DataTraveler SE9 /0/1/0.0.0/0 /dev/sda disk 7756MB /0/2 scsi1 storage /0/2/0.0.0 /dev/sdb disk 240GB Corsair Force LE /0/3 scsi2 storage /0/3/0.0.0 /dev/sdc disk 3TB ST3000DM001-9YN1 /0/4 scsi3 storage /0/4/0.0.0 /dev/sdd disk 3TB WDC WD30EZRX-00S /0/5 scsi4 storage /0/5/0.0.0 /dev/sde disk 3TB WDC WD30EZRX-00M Array Devices: Disk0 sdg is a Parity drive named parity Disk1 sdl is a Data drive named disk1 Disk2 sdc is a Data drive named disk2 Disk3 sde is a Data drive named disk3 Disk4 sdf is a Data drive named disk4 Disk5 sdh is a Data drive named disk5 Disk6 sdk is a Data drive named disk6 Disk7 sdi is a Data drive named disk7 Disk8 sdm is a Data drive named disk8 Disk9 sdj is a Data drive named disk9 Disk10 sdd is a Data drive named disk10 Outputting free low memory information... total used free shared buff/cache available Mem: 12182180 1059756 10481732 368392 640692 10418612 Low: 12182180 1700448 10481732 High: 0 0 0 Swap: 0 0 0 *** END OF REPORT ***

Deletes don't matter. The entry in the hash file will still exist. If the file gets recreated then the hash will get updated automatically Sent from my LG-D852 using Tapatalk

Okay, wow. I appreciate the info. What's the general consensus, do I need to target 6.1.9 too? I understand the reservations to upgraded to a remotely authorized version, but I'm hopeful 6.2 final is close at hand. Paul Its your script - you decide. v2.2 with the mods I posted does work fine on 6.1 I have no choice but to downgrade the one server if only to verify CA compatibility with 6.1 for at least 6mths after 6.2 goes final.

I wouldn't be opposed to you running this on 6.1.9. I'm curious how it would behave. No idea if it is compatible, though, so no pressure. I appreciate the extra effort!!! Your Short Auto results look very promising. Can't wait to the the result of the Normal Auto. Thank you thank you thank you. I tried to use unix2dos, but found it wasn't installed and gave up. I was frustrated with the idea of having to modify all the echo statements to get the new lines. Good catch, that's my mistake. I pulled the Fastest/Thriftiest/Recommended calculations out of the Short Auto test, but failed to pull the ability to Apply or SAVE the values from the Short Auto run. You definitely should NOT be saving or using values from the Short test, it's just not accurate enough. I'll fix for the next beta. Thanks, Paul

Since this would have affected me (the rename) (good catch -> never noticed it) I've fixed it... Updated to 2016.08.26 As far as editing in nano with no changes being made and a scan being issued, its because nano opens files in rewrite mode. Once the file is closed, the only way to tell if the file was actually changed is for a scan to take place (since the filemtimes don't actually change, no actual update of the hash will take place)

Its exactly what it says. FCP was unable to download an application feed (the same feed which CA uses), so it couldn't perform those tests. Usually in conjunction with this there are also errors about connectivity, but occasionally there are not (due to various other factors such as your VPN provider blocking cloudfare, etc)