That's incorrect. chmod is possible with NFSv4 ACLs depending on aclmode.It would require manually setting the permissions, but we had reports that it is technically possible.
NFSv4 is a bit tricky: Even if, for example, our automatic permissions system would have support, a lot of containers try to do things like CHMOD, which are not possible on NFSv4 datasets.
The default aclmode, when SMB-Share mode is picked on dataset creation, does not seem to allow that. We've also recieved similair reports when people imported a core pool.That's incorrect. chmod is possible with NFSv4 ACLs depending on aclmode.
The default aclmode, when SMB-Share mode is picked on dataset creation, does not seem to allow that. We've also recieved similair reports when people imported a core pool.
We've had about 20 users by now scratching their head about it and our automatic chmod scripting erroring out.
It's awesome to know it technically could work, we 100% agree there, but as a project, we just had too many issues with it to be able to support it.
Please be aware we can only speak for our own project (and containers), not for TrueNAS or iX Systems.
What automatic chmod script is this?The default aclmode, when SMB-Share mode is picked on dataset creation, does not seem to allow that. We've also recieved similair reports when people imported a core pool.
We've had about 20 users by now scratching their head about it and our automatic chmod scripting erroring out.
It's awesome to know it technically could work, we 100% agree there, but as a project, we just had too many issues with it to be able to support it.
Please be aware we can only speak for our own project (and containers), not for TrueNAS or iX Systems.
This is not really related to this topic, We just wanted to make clear we currently do not offer active support when using NFSv4.What automatic chmod script is this?
What do you mean by this specifically? Middleware does not currently allow users to specify NFSv4 ACL type for applications dataset. Are you referring to not supporting users mounting datasets with NFSv4 ACLs in containers (i.e. PLEX movies)? That seems arbitrary. Are you changing permissions on datasets that are mounted in containers?This is not really related to this topic, We just wanted to make clear we currently do not offer active support when using NFSv4.
Like many other big helm repositories, we do offer automated permissions solutions and some containers actively require CHMOD being available upstream. Those two issues combined lead us to, for the moment, not offering live discord support when running NFSv4.What do you mean by this specifically? Middleware does not currently allow users to specify NFSv4 ACL type for applications dataset. Are you referring to not supporting users mounting datasets with NFSv4 ACLs in containers (i.e. PLEX movies)? That seems arbitrary. Are you changing permissions on datasets that are mounted in containers?
Is there any plans to change middleware behavior and to accept NFSv4?What do you mean by this specifically? Middleware does not currently allow users to specify NFSv4 ACL type for applications dataset. Are you referring to not supporting users mounting datasets with NFSv4 ACLs in containers (i.e. PLEX movies)? That seems arbitrary. Are you changing permissions on datasets that are mounted in containers?
You perhaps misunderstand me. POSIX ACLs are forced for the dataset ix-applications. ou can mount datasets with NFSv4 ACLs in a container and as far as I know, it works as expected. The only gotcha is that you need to configure permissions for the relevant processes in the container to read / write data.Is there any plans to change middleware behavior and to accept NFSv4?
You perhaps misunderstand me. POSIX ACLs are forced for the dataset ix-applications. ou can mount datasets with NFSv4 ACLs in a container and as far as I know, it works as expected. The only gotcha is that you need to configure permissions for the relevant processes in the container to read / write data.
For example, if you have a "media" SMB share and wish to expose it to plex, you can configure so that the builtin_users group has MODIFY access (inheriting), and then look at id of the plex user in the container (I believe it is 972), and grant that id MODIFY with INHERIT as well. This can be accomplished with our webui permissions manager.
> Two projects, two different opinions on what is considered stable, which is totally fine :)
The behavior regarding chmod and the ZFS aclmode property is no different than in FreeBSD and Illumos, it has nothing to do with stability. It just requires a familiarity with underlying filesystems and operating systems.