Jump to content

sirkuz

Members
  • Content Count

    49
  • Joined

  • Last visited

Community Reputation

2 Neutral

About sirkuz

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. It's not a "show stopper" issue. Backporting would be silly...wasted dev time IMHO. The fact that they acknowledged and fixed in next major rev makes me happy. I don't have anything configured for 6.7.x that prevented a downgrade and I doubt most do.
  2. Interesting find. Setting the same on mine has helped a lot as well. Thank you!
  3. Has anyone compared speed of the mover script in 6.6.x vs 6.7.x?
  4. I bit the bullet and have decided to revert one system as well, as reported many times things seem to be back to "normal". Not sure how long I will be able to hold of on the secondary reverting as well as it was quite simple.
  5. Good to hear reverting back helps. I am trying to hold off for a fix but this sure is an annoying issue! Been following/researching it for awhile but now that more people are reporting it hopefully it will get some more attention/resolution
  6. Any chance this is issue is more related to the rsync application more than anything? The same issue described here happens for me with Plex/Emby using unbalance plugin as well....also rsync. Anyone take a stab at rewriting either plugin to use rclone? I get much better performance on my scripts using rclone for file moving processes.
  7. Generally speaking it allows you to adjust the allocations for your tmpfs. See: https://wiki.archlinux.org/index.php/Tmpfs Specifically for me I adjust how much can be allocated to my /tmp and other locations. I believe the default is to only allow up to 50% for the /tmp directory. I have a lot of memory so I allocate much more to it. Here are my settings from my go #resize some directories mount -o remount,size=192G / mount -o remount,size=6G /run mount -o remount,size=6G /dev mount -o remount,size=6G /sys/fs/cgroup mount -o remount,size=384M /var/log Someone else much more knowledgeable with linux might be able to chime in and correct any mistakes in the post. I cobble my information together and not always perfectly
  8. I'd like to see the option in settings to adjust how the system memory gets allocated. Currently I do this with the mount -o remont,size= in the go script. I think having the ability to adjust how unraid assigns this would be great for power users. Maybe there is a plugin I haven't come across yet, but will add this request here in the mean time.
  9. Any chance someone could post these somewhere else again? Seems like the free download period has ended. Much appreciated!
  10. can anyone tell me what version of mlx4 driver is in this one? I had to run lowly copper/gigabit because the mlx4 driver kept crashing my system every couple days in 6.5.1
  11. Same here, new behavior when the system runs low on available ram it's crashing. Had this setup since v6 release and no problems until I think about 6.4 rc15 or so. Docker engine running out of system memory shouldn't be bringing down the entire array.
  12. same problems here with the transcoder set to /tmp in this build
  13. Picked up some of these and was excited at the prospect of throwing them in for cache drives in my systems but they do not work on unraid. I know its a long shot but was hoping support could be added. LOVING the way 6.4 is shaping up! Ready to upgrade my license to support more drives. https://support-en.sandisk.com/app/answers/detail/a_id/457
  14. This feature alone makes 6.4 so worth the wait. As soon as its released I am upgrading my second license just for the heck of it so I have two pro versions for my live and my test machines.