nivrix

Hi everyone, I’m currently running a Backblaze Personal Backup container. In this setup, my entire user directory (/mnt/user/) is exposed and passed as a virtual drive to the Backblaze Personal Backup software through a Wine environment. Everything works fine so far. However, there’s one thing I would like to change: I want my disks to spin down again. Currently, that’s not happening because the Backblaze container creates a .bzvol folder in the root directory of its virtual drive (/mnt/user/.bzvol). When I create a hidden folder in the Unraid user directory, it automatically gets placed on the first disk. This hidden folder is actively used during uploads, meaning that Disk 1 remains active constantly, even if the data is only being uploaded from the cache. I’ve already tried deleting the .bzvol folder and recreating it directly in the cache array. The issue is that when I expose the user directory and mount it as a virtual drive in Backblaze Personal Backup, any write operations in this .bzvol folder are automatically directed to Disk 1, even though the folder was initially created in the cache. Creating a "hidden" share with primary storage to cache also does not work, because you cant start the share name with a dot. I also tried working with symlinks. First, I created symlinks using the Unraid terminal, outside the container but they pointed to incorrect directory paths inside the container. Then, I tried creating symlinks directly within the Backblaze Personal Backup Docker container, but that didn’t lead to success either. To be more specific, I created a share called bzvol (/mnt/user/bzvol) and set its primary storage to cache. I then created the .bzvol folder here (/mnt/user/bzvol/.bzvol) and created a symlink from this .bzvol folder to the root directory of the virtual disk in my case the user directory (/mnt/user/.bzvol). Unfortunately, this didn’t work as intended either. The only solution I can think of is to pass each individual share as its own virtual drive to the container. However, I would prefer a solution that includes the entire user directory so that new shares are automatically included without further adjustments. Maybe someone has a creative solution for how to implement this. Any help would be greatly appreciated! Thanks in advance! Link to project (Available in Unraid Community Applications): https://github.com/JonathanTreffler/backblaze-personal-wine-container

I had a similar issue and solved it with a RAM upgrade. More details here: Btw I still have read accesses to the bzfirmware file but there is no utilization shown in the web interface or in netdata. Here is a example how it looks just filtered for bzfirmware with inotifywait --timefmt %c --format '%T %_e %w %f' -mr /boot | grep bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:24 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:27 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:28 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:32 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:32 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:32 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:32 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:37 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:43 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:43 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:43 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:43 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:43 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:51 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:45:52 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:46:01 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:46:01 2024 ACCESS /boot/ bzfirmware Fri Aug 9 12:46:01 2024 ACCESS /boot/ bzfirmware

Hello, I think I had the same problem and was searching for a solution for a long time but couldn’t find one. I experienced the exact same issue with increased read access on the USB stick. After a server restart, these accesses increased over hours and days until the USB stick was fully utilized, causing the web interface to crash (php-fpm crashes in log) and become inaccessible regularly. Also the CPU load was shown near 100%. I managed to solve the whole problem by increasing my RAM from 8 to 32 GB. In my specific case, the mainly Backblaze Personal Backup Container caused the issues, but i guess other applications that also used RAM in combination with this container contributed to the problem. Now after the upgrade to 32 GB I found that the Backblaze Container was very RAM-hungry, and my previous RAM capacity was insufficient for the proper operation of the container. I believe it had something to do with the RAM since the problem is now resolved. I should also mention that even when my RAM was still at 8 GB, it was never fully utilized. I believe it never exceeded arround 80% usage, yet the issues mentioned above still occurred. Another thing that comes to mind is that I also tried, as suggested in other threads, to monitor the read operations on the USB stick. I found that numerous read accesses occur on the USB stick, regardless of whether the web interface shows a high read load or not. Unfortunately, I was not able to determine which specific read operation was primarily responsible for the high read load. However, I can say that many read accesses on the USB stick do not necessarily cause a visible write load and are not necessarily mainly responsible for the problem. Up until now, I've been using more RAM for 3 days and the problems have normally occurred by now at the latest. I'll let you know if this changes again. Good luck, maybe this will help!