[[Support] HaveAGitGat - Tdarr: Audio/Video Library Analytics & Transcode Automation]

On 5/4/2020 at 1:10 PM, jstembridge said:

Same issue with continuous disk writes for me too. iotop shows that it's mongodb:

  TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND                                                   
 5279 be/4 root        0.00 B/s 1771.71 K/s  0.00 %  0.44 % mongod --config /etc/mongodb.conf [WTJourn.Flusher]

 

Moving the tdarrdb directory off the cache pool fixed it for me. If it sits directly on the array or on a unassigned drive then it's only writing about 4KB/sec. I have no idea why this fixed it.

[Large copy/write on btrfs cache pool locking up server temporarily]

I also experienced this same issue with my two Samsung_SSD_840_EVO_250GB drives that I had in BTRFS RAID1 for my cache pool. Large file transfers would cause insane iowait. System load would shoot up to 60-80. Docker containers and the Unraid web-ui would become entirely unresponsive.

 

Since moving the pool from raid1 to single, the issue seems to be gone. With 6.9 reportedly having the option for multiple cache pools, I would really like to revisit the option for a mirrored cache pool.

[[Support] HaveAGitGat - Tdarr: Audio/Video Library Analytics & Transcode Automation]

I'm having an issue where this container is constantly writing about 2Mbyte/sec, even when idle. No workers are currently running, they only run in the middle of the night. When I stop this container, the writes to the cache pool are anywhere from 0 to 300Kbyte/sec. While tdarr_aio is running, it is anywhere between 1.8-2.4Mbyte/sec. Any idea what could be causing this?

[[SOLVED] read_folders error]

I too am getting this error all of a sudden.

 

screencap and diagnostics attached.

 

The error appears on both the Dashboard and Docker tabs. The server seems to be functioning without problem otherwise.

 

I believe I've already isolated the issue. I had recently updated several community apps, including the Docker Folder plugin. I removed that plugin and the error no longer comes up.

 

tower-diagnostics-20200501-1821.zip