slimshizn

I see you added this along with fast list. What is the IP? Is that Plex? Going to try it out myself. Edit: Found your reasoning in the rclone forums.

Just wanted to update, haven't had a single call trace since I turned off the custom IP containers. Now that things have calmed down I'm going to try your br0.3 idea.

Well I did try to increase rx and tx buffers and had some interesting results that didn't happen before. Using ethtool -G eth0 rx 8192 tx 8192 I had this happen. As you can see I got a little carried away at trying to use the command lol. Hope that this can help reproduce this issue for bug zapping. Edit: Interestingly enough I tried this on my other server and it passed it through. Edit 2: Updated to 6.6.3, reboot the server, ran ethtool -G eth0 rx 8192 tx 8192 and it went through without a kernel panic. Testing speeds again.

I have a Mellanox NIC on another server as well and have seen kernal panic once. This was without the use of a user defined static IP for dockers, which makes the argument of docker br0 being the issue a little more difficult. Being that it was a one time occurrence and didn't cause the system to lock up, I'm going to think of it as a fluke.

I can give this a shot and see what happens, I'm not opposed to testing if it fixes the issue. I am on 6.6.2 at the moment but now that I have seen another call trace (thought it might have been fixed in 6.6.2) I'll go ahead and update after the parity check. Also the driver is Mellanox, I believe that is the mlx4 referenced above.

I'm going to try and reproduce the problem on a different server.

Was going good for about a week now. I was told this was fixed in a previous version of Unraid, but today it caused my server to lock up completely making me do a unclean shutdown (parity check as we speak). I can't have that happening so I'm shutting down any fixed IP docker containers hoping that it will fix the problem. I'd like to put this down as a bug but need someone's verification before I do so. Thank you. Here's the Diagnostics. tower-diagnostics-20181024-1640.zip

I've updated to the latest, still having issues after rebooting with the folder caching being disabled and the function on enabled. Stopping and starting it still fixes it.

I had the same issue, removing and reinstalling fixed the issue, works fine. Haven't rebooted to see if it happened again.

This has been awesome, getting speeds up to 40 MB/s with this on ( after delete and re download ).

Getting can't follow symlink without -L/--copy-links. I've searched up on rclone forums and came across a github issue. Seems this wasn't working as of April, anyone know if adding -L fixes this issue yet?

I have a couple non Samsung's btrfs raid 1 and it still bogs the system down a bit. Not unusable but noticeable when trying to do things. Netdata shows between 7=10% iowait with mover going and spiking to 25%. Typically don't even worry about it due to the run late at night, but now after reading about some of this makes me want to raid 0 it or go to xfs and add the additional to unassigned devices for a VM.

Getting some lock ups using the automation feature. Using BLAKE2, FS is XFS. System : M/B: Supermicro - X9DRi-LN4+/X9DR3-LN4+ CPU: Dual Intel® Xeon® CPU E5-2660 v2 @ 2.20GHz

After a server reboot it was updated.

Yeah, I have 1.41 installed right now (not latest). It's not showing an update on the plugin page.

If I have the stable downloaded, is there a way to update that to a version with cache or transfer to the beta version?

Having this issue go on sometimes. Sometimes after a reboot it doesn't show up but sometimes it does. May 29 21:39:23 Tower kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! May 29 21:41:54 Tower kernel: i801_smbus 0000:00:1f.3: Timeout waiting for interrupt! May 29 21:41:54 Tower kernel: i801_smbus 0000:00:1f.3: Transaction timeout May 29 21:41:54 Tower kernel: i801_smbus 0000:00:1f.3: Failed terminating the transaction May 29 21:41:54 Tower kernel: i801_smbus 0000:00:1f.3: Transaction failed May 29 21:41:54 Tower kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! This then stops and doesn't happen again while the server remains on, only after reboots. Currently running 6.5.2. Followed all instructions before upgrading.