jnheinz

Hi jnheinz, well gracefully isn't possible. I'd do killall rsync killall unbalance You'd be left with a partially copied folder. The log will tell you which folders were copied and which one was in progress. Then you'd have to do some manual tending after (delete the partially copied folder on the target disk maybe?) Ok, thanks. I will probably hold off. Thank you for this plug-in, it has been very helpful. Unrelated question, I'll lay out the scenario to see if this is something unBALANCE can handle. I have a share called TV shows that is roughly 5TB in size, spread out amongst about 6 disks currently. I have three 2TB disks that are empty that I would like to migrate these shows to. However, I do want to observe the correct split level.. which is keeping the entire series together, so I have it set to split the top level only now. I don't think it was set this way when it was originally copied, so the data has ended up everywhere. In unBALANCE, If I go through each source disk with tvshows selected & select the 3 target disks.. Does it observe the split level? Or will I need to split manually? Am I better off moving them all out of the share & back in? Looking for the most efficient approach to this.

Is there a way to gracefully terminate an unBALANCE job in progress?

Thank you for this docker, works great thus far.

Dumb question.. if I change the Included Disks from All Disks to Disk 20 on a share that is currently spread on Disks 1, 13, & 22.. Will just new data go to Disk 20 & the old data on Disks 1, 13 & 22 still be accessible? It doesn't actually move all the data to Disk 20 does it? Just talking about the settings of a Share. Thank you for this plug-in, it helps me move stuff around.

I am about to run through his stuff using a quad-port NIC. I think you skipped the MAC address & NIC model configuration.. So it likely presented your NICs to pfSense as Realtek (which suck for BSD). If you use e1000 in his example, I don't think the checksum offloading should be an issue.

Thank you sir, this helped a lot. I was fighting permissions issues. Excellent docker, thank you for your work.

Is there any way to prevent this Docker from making a "default" file/configuration when restarted under /config/nginx/site-confs ? It is messing up my reverse proxy configuration. I delete default & it then works. Kind of a pain.