Can you please verify if the issue is fixed when we re-add the After=zfs-mount.service?
Beiträge von votdev
-
-
This command is only available in OMV5.
-
Note, i only got it running after i've enabled 'No session reuse required'. See https://stefankonarski.de/cont…te-nicht-empfangen-werden.
-
You've hit a bug. Will be fixed in openmediavault 5.0.9, see https://github.com/openmediava…9289fd93ea441c3e2758cdf53.
-
Have never seen that, but maybe Google can help you.
-
The root filesystem is surely full.
-
Probably it is not necessary, but people do it if they are not aware it will cause problems. So maybe an error message when creating the label would help. At least in those cases where the label is added using OMV.
The OMV UI does not allow blanks for labels when creating new filesystem since ages.
-
I've opened a bugreport in SaltStack: https://github.com/saltstack/salt/issues/54508
-
It seems to be that SaltStack can not handle blanks in device names and mount dirs properly. Need to find a workaround and maybe a bug fix for the upstream project.
I really can’t understand why it is necessary to use blanks in filesystem labels or file names. As SaltStack has it’s problems with it i think blanks in filenames are not widely used in Linux and it seems to me that this absurdity comes from the Windows world.
-
You've found a bug. Filesystem labels with blanks were not handled properly. Fixed in openmediavault 5.0.8, see https://github.com/openmediava…1c38188f45b30dfbbea38dc57 and https://github.com/openmediava…cf5184f624cce8b67dece6b83.
-
does it mean that plugins like rsnapshot or nginx should point to /srv/xxx/yyy and never to /sharedfolders/yy ?
Yes
-
The problem is that the mount point configuration is not valid, this seems to be raised by an invalid shared folder name.
-
Please provide a detailed step by step instruction how we can reproduce this issue. Starting from creating the shared folders (names, paths) and so on.
-
-
-
Pease read the changelog for the shared folders feature. There you will find the note that the /sharedfolders directory should only be used in cron scripts or when you work on CLI, but nothing else because of the problems you have at the moment. These folders are only shortcuts, no additional abstraction layer.
-
Das geht auch nicht über die UI. Die Shared Folders werden erstellt, alles andere wird über services wie FTP und SMB gemacht.
Du kannst aber Shared Folders in Shared Folders erstellen, vielleicht hilft dir das ja weiter.
-
With OMV5 there is a little little little solution for that, but i didn't have tested that till now and i'm sure it needs some help and contributions to get it running.
With the command
you can rebuild all configuration files and start/stop the services with one command. BUT as said, there might be some problems, e.g. some things are assumed to be done by the backend at runtime, e.g. creating directories and so on. But i think nothing that can not be fixed, but help is needed to do so.
-
-