woble

Switched to XFS, rebuilt the docker.img with the same dockers as I had before. Now `loop2` is around 9-30MB/min. For those who are still on BTRFS perhaps it's worth trying removing the docker.img and re-adding all dockers. It might help. I should have tried that first. My original post: https://forums.unraid.net/bug-reports/stable-releases/683-docker-image-huge-amount-of-unnecessary-writes-on-cache-r733/?do=findComment&comment=9019 Edit: after having it run for almost a day, the `loop2` write seems to be stable at around 1.7GB/h.

Unraid 6.8.3 Cache: Crucial MX500 2TB SSD - BTRFS w/o encryption Just want to chip in and say that I have similar issue, write on the cache drive hovers between 5-10MB/s constantly. `iotop` reports huge amount of writes to `loop2` for no reason, or so it seems. I disabled all active dockers and started enabling them one by one to see how it affects `loop2`. Out of all dockers that I have, `nginx-proxy-manager` seems to have the most effect on it. Without it `loop2` writes around 100MB/min and the cache drive in the UI shows as low as few KB/s or even 0 for writes, which is for a total of 14 dockers, arguably some of them aren't that heavy to begin with or don't do much IO in the first place. Those 100M might be related to the dockerd logs which are reported as `dockerd -p /var/run/dockerd.pid --log-opt max-size=10m --log-opt max-file=1 --storage-driver=btrfs --log-level=error` in `iotop`, althogh these report less than 1MB/min. Then there are `shfs /mnt/user -disks 4095 2048000000 -o noatime,allow_other -o remember=330` processes which report 2-30MB/min. With `nginx-proxy-manager` docker enabled (plus all the other dockers), the write to `loop2` jumps to around 400MB/min, the dockerd log processes go to around 2-3MB/min, and shfs ones jump to 70-90MB/min each. I used to have 6 Crucial SSDs in RAID10 for cache, which ran for about 2 years. Upon inspecting them with Crucial tool, all of them reported around 260TBW which is crazy high for 2 years of really not that intensive load. I've seen people mention `pihole` and `nzbhydra2`, which I also run, but they don't seem to affect it overall as much as `nginx-proxy-manager` does.

You can roll back to `1.4.7-1-01` by changing the repo to `binhex/arch-nzbhydra2:1.4.7-1-01`. Anyone else experiencing v2 crashing and needing to restart the docker? Happens to me every few days or so. Unsure if it's related to the beta state of hydra or the docker itself.

Hey @binhex Is upgrade automatic with the newest releases of nzbhydra2 or do you have to upgrade the docker manually for us to get the new version?

@dmacias Fair enough. In regards to versioning. Is that an automatic or manual process? I noticed for example that borgbackup is already 1.1.4 while still 1.1.1 in nerdpack without any upgrade option. How does one upgrade all tools to the latest?

I had that same problem initially with the other docker, but lidarr fixed the issue a while ago. Ref: https://github.com/lidarr/Lidarr/commit/aab78a62e68b28fd7115ae69edf5b704456f6389 I also have the following script running daily to clean up the docker logs. #!/bin/bash logs=$(find /var/lib/docker/containers/ -name '*.log');for log in $logs; do cat /dev/null > $log;done

Is there a way to use `nightly` instead of `develop` branch of Radarr. Perhaps a separate docker is required for that? Same goes for the nzbget, `develop` instead of `stable`, and sonar. Any chance you could create those dockers if there's no way with the current ones.

How about adding https://github.com/rg3/youtube-dl/ ? Fairly easy to install manually, but I am sure some lazy hoarders will appreciate.

There's an issue with the footer where it floats on top of long lists. Apparently was brought up before but never fixed. Easy to fix as follows. 1. Change `height` on the `body` class to `min-height`. This will have the footer at the bottom of the viewport if there's plenty of space, otherwise other content will push it down outside the viewport. 2. Remove use of `height100` class. It relies on viewport height and unnecessarily clamps the height of a block that is taller than 100vh.

If preferred way is docker or even a full blown VM, why not remove FTP from unRAID completely. In its current limited state it's pretty much useless from my own experience.

There's no right or wrong answer. It's whatever works for your server really. Sent from my SM-G920F using Tapatalk

Can HTTP still be used as default or is HTTPS mandatory now?