Droidguy759

Thanks for the reply and thanks for the help. With this being the intended function, storage locations of docker containers such as Minio will always be left with hundreds or thousands of empty folders after running the mover. Nearly every file created within a Minio storage location is created within multiple nested folders. As new files are added, they are placed within newly created nested folder structure. Therefore it would seem the tuning plugin will always leave many empty folders after the mover runs. Is there another mechanism to remove the empty folders left behind or should I look towards writing a script to clean up those empty folders?

Regarding this issue of "Clean empty folders", I am able to replicate the behavior of empty folders being left after the mover runs mentioned by steve1977. I am unsure if the behavior that I am seeing is actually the intent of the developer. The description of clean empty folders states "This will remove the parent folder only of moved files". This verbiage leads to the assumption that the intended behavior is only to remove the direct parent folder of the moved file and if a file is nested within multiple folders only the direct folder containing the file will be removed and the other empty parent folders will remain. Such as /mnt/user/app/test1/test11/test111/testfile.txt. After testfile.txt is moved only folder test111 will be cleaned but the parent nested folders test1 and test11 will remain even when empty. Is this the intended function or should all of the parent folders be moved and cleaned without leaving empty folders?