thomast_88

I'm still having issues. Copied a 11GB file from my primary array, to the cache array (raid 1), and server load went to 25'ish before it ended, making my dockers / VMS crash. @johnnie.black I saw your tests earlier, and noticed you are using raid 0. Have you had any issues with raid 1, or maybe have any idea why this is happening? @aptalca did you get all the issues fixed - and are you running raid 0 or raid 1?

Before: Total devices 2 FS bytes used 186.99GiB devid 1 size 232.89GiB used 232.88GiB path /dev/sdc1 devid 2 size 232.89GiB used 232.88GiB path /dev/sde1 After: Total devices 2 FS bytes used 189.18GiB devid 1 size 232.89GiB used 192.03GiB path /dev/sdc1 devid 2 size 232.89GiB used 192.03GiB path /dev/sde1 Trim: fstrim -v /mnt/cache /mnt/cache: 81.7 GiB (87732568064 bytes) trimmed Not sure what those numbers exactly mean, but so far I feel a performance improvement - that is promising! I will try with some large files tomorrow :-)

@johnnie.black I will test this straight away when I get home. Thanks for putting your findings up!

I have a BTRFS raid1 (2x250gb Samsung EVO), and I'm having the same issues as @aptalca for months. Raid is unusable when copying / moving stuff. If anybody got an idea how to trace this down, let me know. I'm willing to invest my time to get this fixed.

I think this is a serious bug which should be adressed. Isnt BTRFS the recommended way to run a cache array? Right now it's working poorly with all these crashes on large writing of files

Hmpf - thanks for the quick reply. I'm hoping someone can step in with a working solution. I'd really like to utilize the btrfs raid function without the server crashing

@aptalca Sorry for bugging you. But how is your test progressing? I'm at the same boat as you at the moment. I can conclude running with a single drive, everything works properly. But in raid1, things start to become unstable. This sucks pretty much, as this renders the cache functionality useless. But this has to be a configuration issue? Many people are running with several drives, and they don't report these issues...

Thanks for the plugin, simple but helpful . Using it for unBALANCE currently. Will probably add Krusader as well.

Moving the scripts to a GitHub repo is a start. That will even release you from maintaining the first post = less work.

What about a GitHub repo for all these great scripts? I can help making it. (Feature Req) And have them listed in the GUI as "Community Scripts". Just like the CA plugin.

@aptalca did it help?

Since 6.3 for me. I already posted an issue half a year ago about this.

Any ideas how we can diagnose this @johnnie.black? Like @aptalca mentioned, it's hard to do any diagnosis, as the system is unresponsive when it happens. I can easily reproduce this by writing a large file to the cache array, but then the system becomes unresponsive (load average keeps raising). I basically stopped using my cache array, for bigger file transfers, as this problem is causing the whole system to lock up.

Ok, sounds exactly like the issue i have been having since i changed my cache from 1 to 2 disks :-(. When it's at > 40ish %, VM's / Dockers begins crashing until i stop the write command.

Does "load avarage" when doing the "top" command keep raising when you copy to the cache array? Something similar happends for me. Lock-ups during writes of larger files to the cache array (> 4gb files)

AFAIK the official netdata github repo has a commit hook, so that whenever there is a new commit to it, it's building a new docker image. And as far as you can see in the GitHub commit log, there are daily commits. So it's features / bug fixes :-)

Yep, i found it. Working great - thanks!. I was using before, but it had some bugs which would not allow you to use your keyboard. It works in this one! @Djoss Will you be making one for MakeMKV as well?

Cool, good work. Will you be making a template an unRAID template for this one?

Ohh, so if you're only going to make backups then yes, definitely use that one: This container is only if you wish to mount the cloud files as a volume on your server. E.g. for consumption of the data by other containers.

Yes, the default command mounts it with read-only. I have been following the development of the mount feature on the rclone forums, and unfortunately it doesn't indicate that using the mount for writing is stable (yet). So I would not recommend using it. Instead you can use my other container for writing (utilizing the copy/move feature instead).

@sniper Please post both docker run commands. Both for Rclone-mont and Sonarr. I have it running with Sonarr, so it shouldn't be a problem.

@sniper Are you on IRC or slack? Think it will be easier to debug if we can have a chat conversation I suppose you added the volume /mnt/disks/rclone_volume/Gdrive to the container you want it available in, right?

Read FAQ: I cannot see my mounted volume/files outside of the container Make sure you have this in extra parameters (advanced view): --cap-add SYS_ADMIN --device /dev/fuse --security-opt apparmor:unconfine -v /mnt/disks/rclone_volume/:/data:shared Make sure that this docker container is started before the container you are sharing the volume with.

@sniper sudo chown 911:911 /path/to/mount/folder I will fix this in the docker directly this week.

@sniper Have you added the necessary Extra Parameters as writtin the the OP?