Comment 4 for bug 1848653

I take that last part back. The zfs-mount service is failing to start. I believe I know what caused this whole scenario:

1. I'm running containers on my host, specifically using Docker
2. Many of the containers have volume mounts out to different data sets within my pool
3. It looks like either Docker was not stopped when I started the 19.10 upgrade or it was started up too soon during the upgrade. When all of my data sets were unmounted there were some containers up and running happily writing bits of data into some of the data sets
4. zfs-mount service fails indicating that the mount point is not empty

What I did to remedy this was to go into my mount point and wipe everything out that was there. In my case there were directories created from the container volume mounts, as well as some files within them from some of the applications coming up and writings logs/config (but then crashing as everything else was missing). After the cleanup of the mount point I could start the zfs-mount service successfully, I saw all of my data sets get mounted, and everything is generally working now.