You need to modify the <opts> field in the config.xml file. After that, run omv-salt deploy run fstab.
Ok thanks. I thought modifying the config files was no good as the changes would be lost.
I'll give that a try, Would be great to have it in the GUI though. 
I want to set the umask for a couple of the filesystems. I can find nowhere in the GUI to add mount options. They exist in config.xml, but don't seem to be configurable from the GUI. How can I add special mount options for a filesystem?
I am exporting a couple of shares over NFS, mounted on a Mac (running Monterey). They are working, but some issues I'd like to fix.
First of all, it's using NFS v.3. OMV does support v 4, 4.1 and 4.2, as does the Mac as a client, but the mounts end up v.3. If I try to force v.4 on the Mac, it cannot mount the shares, some vague error about 'permissions', but that can simply mean the shares are not available.
So if the Mac is unable to mount using v.4, that rather suggests that OMV is sharing them only with v.3. Is this possible? In any case, any suggestions as to how I can get the Mac mounting shares with v.4?
If I put the OMV server to sleep, when it wakes, the shares are not available. Can also happen at other times when it has not been asleep. I have to disable NFS in the OMV GUI and save, then enable NFS again and save. Then I can mount the shares. It's not a major problem, but very irritating so would like to find a solution to this also.
Finally, the biggest issue really is that trying to save a file (open on Mac) over the network to the HFS share can be a problem. About 50% of the time, the save fails with a complaint about 'truncation error'. The last 2 times were video files with some minor tag changes and after this error, they were completely borked. Still the full size on the server, but cannot be played. Opened in several video editing apps to try and see if I could recover them, but no chance. As I said, 'borked'.
Fortunately I have been able to obtain good copies to replace them, but clearly this is a serious problem. I've been using networks of various types for 40 years and I don't think I've ever come across an error like this that has actually trashed the file. This exact process (saving tag edited video file) over an AFP or SMB connection to a Mac server has NEVER had any problem whatsoever.
I don't want to ditch NFS and just use SMB. I'd like to get this NFS connection working. Could do with some assistance as to what I need to do in OMV to make it work.
This document should clarify all aspects of mergerfs. If this is not the case, you can say so or propose improvements.
https://wiki.omv-extras.org/do…mv6:omv6_plugins:mergerfs
( crashtest )
That's not really what I was saying. The way OMV presents much of its configuration uses the same visual style and as I have explained above, it does not make clear what information belongs to which 'section'. Yes, If I study it and look closely I can figure it out, but good interface design would make this all obvious at first glance. In truth it is not hard to make clear what relates to what and OMV is somewhat obscure in this regard.
This is not a 'complaint' as such as I really appreciate what OMV provides and enables for me, but should be taken as constructive criticism.
Ah, got it. Had another look at creating a new 'merge' in mergerfs plug-in and Filesystems are not the only possible source. I can add folders (shared or otherwise). So that all looks like I can do what I need.
I have to say that this aspect of the OMV GUI is visually hard to grasp. The lines across the 'page' as first glance appear to delineate different sections, each with description and data entry (text or drop down), but in fact each section 'straddles' the line, with no clear distinction between one section and the next. OMV is terrific, but this is not good interface design. Sorry, I have done a fair bit of interface design/development myself over the years and this aspect of the GUI is a terrible design and makes it hard to grasp what is connected to what and in this case obscured from me what I had previously been looking for. There needs to be a clear distinction between each section, keeping Name, Value and Description in a clearly defined group, and easily distinguishable from other sections.
Anyway, thanks for the prod to look at mergerfs again.
I want to combine a couple of directories to a single 'read only' view. I think overlayfs (now a mount command option) should work. Is there any way to configure this in OMV GUI?
I've had a good look, but cannot find anything relevant. Is there a way of setting this up in the GUI?
Yes I do. I think I had to do that before I could even create the 'shared folders' I need. They are all set up and I've tried various user perms, but no matter what I try, saving via FTP doesn't and rsyncd complains the filesystem is 'read only'.
As I said, I can use plain rsync and that works without problem (as does scp), but neither ftp nor rsync daemons can write to anywhere in '/'.
I need remote access to some directories of the '/' filesystem, Specifically:-
I need ftp access so I can edit config files on my Mac and simply save them. This is easy in BBEdit and I've been doing it for years with my Mac server.
I also need to be able to rsync some files to various locations.
No problem with either of the above when the target is one of the other drives on my OpenMediaVault server, but simply fail when the target is within '/'. In the case of ftp, I can easily open the required file, but although 'saving' creates no error, nothing actually is saved. Rsync however complains about the target being a 'read only' filesystem which is nonsense as I have write access with any user from direct login or ssh over the network and files can be copied/sync'd both with scp and/or rsync when not using a defined daemon module - IOW just direct rsync to the specified folder. No problem.
So, the issue only arises when using 'Services' configured in OMV (i.e. FTP and rsync). From which I figure that OMV is placing some overall restriction on remote access to anywhere within '/'. I sort of understand that this could be an issue for unknowledgeable users and publicly accessible servers, but I'm not ignorant in such matters (just how OMV is doing things behind the scenes) and this is my private home network which if under attack means I've got bigger problems than unauthorised access to my media. So…
Could anyone possibly explain how to allow ftp and rsync(d) access to the root filesystem? Would be much appreciated.
You need to run
Code$ omv-salt stage run prepare $ omv-salt deploy run nginx
Yup, did that.
Logging in to the address I want to use works fine, but when I try to access it via the other address I am trying to block - OMV web gui opens just as happily.
OMV_NGINX_SITE_WEBGUI_LISTEN_IPV4_ADDRESS is set to the address I want to use and I've run all the 'salt' commands that seem to be required, but it's still listening on the address I'm trying to block and the nginx config file shows the listen command is not used for this (not been changed), so I don't even know how it's trying to block that IP address. Whatever, it isn't.
I set the environment variable as per the instructions, but didn't work. Still accepts requests on all addresses.
Is a full restart required?
Allowing the user to enter an IP address in the Workbench page does not make sense because IP addresses may change if you use DHCP for example.
In the above posts you have all necessary information to limit access to a specific interface. Use environment variables to customize the nginx listen directive to the IP you are using or create an iptables rule.
From the OMV point of view all necessary tools are available to make your requirement happen.
Well I completely disagree. To not allow the user to set the listen address because "it may change" is restricting control for everyone just for the sake of those for whom it may not always work. It should be up to the user to configure it correctly (like a server should have a static address set). You could always display a warning in the webgui if the IP address is included rather than simply not allowing anyone to suitably configure nginx.
Not only that, but you then go on to explain how it CAN be done (using an unnecessarily convoluted method), hence negating your previous statement that it should not be allowed.
Nginx provides the EXACT method for doing this and for nonsensical reasons you won't allow it. Yes I know about setting the variable, but that should not be necessary.
Sorry, OMV is a great product, but this is dumb.
I could have been clearer. Indeed, nginx cannot bind to any specific 'interface', but each 'server' definition CAN be bound to a specific IP address which is what I am wanting.
Address and Interface can sometimes get used interchangeably, but in nginx's case, it's an important distinction and as I have just a single address assigned to each interface, in my case they are the same thing, but I understand the difference in nginx.
However that does not change the question of how to restrict the OMV webgui to a specified IPaddress, which CAN be done in nginx using 'listen address:port', but OMV's webgui prevents this from being entered and as we know, editing the underlying nginx config files would only be temporary until OMV overwrote the file which would remove the IPaddress portion.
Why can we not allow the entry of 'address:port' in the webgui so that we can actually restrict OMV webgui to a single address?
It is not supported because nginx can not be limited to a specifc interface only.
Why do you say that? A listen directive in a 'server' block can be of the format:-
listen IPaddress:port
which specifically restricts nginx to that address and port for that 'server' definition. Whatever other 'server' definitions there are, each can be restricted and since OMV's webgui is simply defined in a 'server' block, I see no reason it cannot be restricted to any specified address (that exists for the actual server of course). The only issue seems to be that the webgui prevents you from entering anything other than just a port number.
Admittedly I am no nginxpert, but the documentation seems very clear on it being able to restrict a 'server' to a single IPaddress.
My OMV server has 2 ethernet interfaces and I want to be able to restrict the webgui to just one of them. I can change the port (and have done so), but the nginx 'Listen' directive can accept IPaddress:port which is exactly what I want. However, the webgui does not allow this type of entry in its port section and if I edit the file directly, it will (eventually) get overwritten by OMV.
Can anyone explain how to restrict the webgui to a specific address and if for some reason it's not possible, why? Seems an entirely reasonable configuration so can see no reason why OMV would specifically not allow this, but cannot see how to actually set it up.
I also restarted the server and immediately after writing the above, I thought I'd try to install the plugin again.
It is wonderful the effect that opening a thread to ask for help has on a problem. The install ran straight through without error and I can now configure the ftp service.
All's well that end's well.
OMV been running happily for a few weeks now, but decided I want ftp access. Since it is now a plugin and not automatically installed, I tried to install the 'openmediavault-ftp 6.0-3' plugin, but got a big red error dialog complaining about dependencies.
System was then left with ftp showing as an available 'Service', but trying to do anything with it and web interface just complained about page not being there. So the installation was incomplete and unusable.
Nothing obvious in the logs and ended up removing the plugin.
Not having ftp is not the biggest deal in the world, but it is handy to allow file editing direct on my Mac, so would appreciate it if anyone can help sort this.
OMV is using the settings of /etc/login.defs to filter users that are managed via UI. Have a look for UID_MIN and UID_MAX.
Perfect. Adjusted those and now can see what I want to see in OMV.
Thanks.
As far as I can see, OMV only shows users with a UID >= 1000. This is something of an issue for me, with several users who require UIDs below that threshold. Is there a way to 'adjust' OMV's configuration so it will show all users from e.g. UID 500?
I am running OMV on a board with dual Network Interfaces. I have one use for the machine that I want to limit to one of the NICs, but it looks like OMV is listening on both, port 80. How can I configure the OMV admin interface to only bind to one of the NICs, leaving the other free to use as I want, with any port?
I cannot find any such setting in the admin GUI, nor any config files (but of course that would not be a good idea anyway). Would appreciate it if someone could point out how I can set this.
Thanks.
Having now installed OMV on the M.2 SSD I can see my fundamental misunderstanding. OMV doesn't take over the entire drive and I was subsequently able to also install other stuff (and Plex) on the same partition as per any other *nix.
That means Plex's database is on the M.2, but that shouldn't be a problem and all is running fine.
