Thanks for the clarification. Now I get it.
I was confused because the actual data was still reachable via the /sharedfolders/ directories. It changed only after a reboot.
OMV 5.3.3-1 disabling /sharedfolder/ feature - why?
-
- OMV 5.x
- nick2k3
-
-
I was confused because the actual data was still reachable via the /sharedfolders/ directories. It changed only after a reboot.
Disabling the feature just removes the bind mount files and doesn't remove the mounts (as you found).
-
Disabling the feature just removes the bind mount files and doesn't remove the mounts (as you found).
What you describe is the behavior after reboot.Before the reboot, the bind mount was still active making all data still reachable from /sharedfolders/XXX/
-
What you describe is the behavior after reboot.
Before the reboot, the bind mount was still active making all data still reachable from /sharedfolders/XXX/
Notice I said bind mount files (found in /etc/systemd/system/) not the bind mounts themselves. So, yes, the data is still reachable.
-
Is is safe to remove "/sharedfolders/" directory after an upgrade to OMV5 from OMv4?
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!