I've watched this thread for nearly a year when the same thing started happening to me and there have been no further updates or indication that this has any priority. I too am going to have to abandon using CloudDrive for this continual dismount issue caused by the host disk being filled and dismounting the CloudDrive until the system is rebooted. I have a daily reboot configured to try to mitigate this but even that is not frequent enough at times. It is sad though, due to the fact that it does work and perform very well for my needs otherwise. I still will use DrivePool and Stablebit Scanner on my other systems as they have been very dependable for me. I have CloudDrive implemented with DrivePool and the plugin to control file placement so that my single host disk acts as the initial local writable space in the DrivePool until the balancer moves the data to CloudDrive. If the host disk did not continually get full with sparse files which triggers the crash and dismount of the CloudDrive it would be perfect for my needs. I've had to resort to building a much more complex Linux solution that offers nearly the same functionality I need using rclone and unionfs-fuse. The only really bad thing is that trying to get a large amount of data out of CloudDrive will only trigger the sparse file dismounts more frequently.
