Burbsi

is there a limit when moving files from one disk to another disk? in my experience i tied to move 2500 files @ ~1GB with only that job in the queue: the process will not start within 4 Hours. So i tried 5000 files @ ~1MB directly, with the move button: does not start within two hours. It says "Running..." but in both cases the CPU is not really doing anything and the disks will spin down since there is no activity. The dialog box can't be recovered and on the bottom there is no status indicator. I've read through this entire topic so i checked /var/tmp/ and there is only a file.manager.active entry the other two are not present. running UnRaid 6.11.5 (Stable) and DFM 2023.06.01 i just don't get it, this would be an at least noticeable job for the CPU just regarding the parity operation part and the drives would also show at least some use since the file table probably needs to be "established" before moving but both are not showing any sign of use while my ram is also only at 12% utilisation. additionally the files are not being accessed by me or docker and no mover or parity operation is running

The S1 sleep state already shuts the processor clock off and stops the bus clock. Meanwhile Dynamix S3 Sleep is an even deeper sleep state - so your docker files may be saved on your cache drive but with your cpu asleep, they don't run. The only thing you can do in S3 sleep state is getting power from USB 3 ports and wake the system up with a button press on the keyboard or a magic packet (wake on LAN). If your question was about keeping docker containers running after the system woke up from a sleep, then the "autostart" feature from the docker tab in unraid should help with that, i have not used sleep after i installed a docker that i want to have running 24/7