OK, I will admit up front that some of the naming in my system set up is probably strange to long-time Linux/UNIX admins, but it all is allowable according to the rules.
Recently when removing a package I no longer use it threw a couple of errors with the remount-filesystems script failing. Looking at the script, I can see why.
The script scans /etc/fstab and issues a mount for the filesystems using the first parameter in each parsed line. However, there are a number of constructs that are perfectly legal to use in /etc/fstab that do not work when issued by the mount command. In my case, here are 2 examples:
/poolmount/Data? /MyPool fuse.mergerfs atomic_o_trunc,auto_cache,big_writes,default_permissions,allow_other 0 0 /MyPool/F1\040Grand\040Prix /var/lib/nethserver/ibay/F1_Grand_Prix none defaults,bind 0 0
Perhaps the script can be changed to use the second parameter of each /etc/fstab line instead, as I think that will always be acceptable to a mount command. Unless anyone knows differently.