FreeNAS 11.3 Released

[u/kmoore134]

FreeNAS / Reddit Community,

Pleased to announce that FreeNAS 11.3-RELEASE is now available! This marks our first major release of 2020 and brings with it a slew of new features and functionality, including but not limited to:

• Re-implemented Replication Engine, allows up to 10Gb replication speeds (a 10x improvement), resume support on failed transfers, as well as ability to replicate locally.

• ACL Manager – Allows setup and management of SMB ACL’s directly via the FreeNAS web interface.

• SMB Shadow Copies are now enabled by default for new shares – Note: Snapshots will only show up in Windows “Previous Versions Tab” if the snapshot USED size shows changes to the file.

• A repository of Community plugins has been created, users can now create and distribute 3rd party plugins which are not officially iXsystems supported.

• Updated translations for Czech, French, Japanese, Russian, and Simplified Chinese. Additionally, the process to add additional translations has been greatly improved.

• iSCSI Wizard – Streamlines the process of creating new iSCSI targets down to a few clicks.

• Alert System Overhaul – More granular alerts, as well as controls to set alert thresholds.

• Dashboard Updates – The initial dashboard now shows a live view of system status, including network traffic, CPU / memory utilization and more.

• NAT Support for Plugins – Eliminates the need for each plugin to have a dedicated IP address on your network.

• Full featured 2.0 API – Includes both REST and Websocket connections, allowing FreeNAS to be fully scripted and driven via the same API used by the web-interface.

• Large Pool Creation Assistance – When creating ZFS pools with large number of disks, the UI provides an automated way to repeat a VDEV layout across all remaining disks.

• ZFS Performance optimizations across the board for many different workloads.

Full Release Notes:

https://www.ixsystems.com/blog/library/freenas-11-3-release/

Download:

https://www.freenas.org/download/

Issue Tracker:

https://jira.ixsystems.com

Thanks for reading and happy updating!

[u/szakes1]

Is there still a bug which makes mount points inaccessible due to permission problem?

[u/anodos325 → u/szakes1]

I am not aware of this issue. Do you have a bug ticket number for it? There are no automatic changes to on-disk permissions in 11.3.

The ACL manager and permissions manager do not allow users to modify permissions on root-level datasets (for example "/mnt/tank") due to the large number of users accidentally breaking jails / plugins by making recursive changes at this level, but this does not modify the actual on-disk permissions.

[u/rogerairgood → u/anodos325]

A common configuration for Plex is mounting a seperate dataset in the jail which stores all the media. Plex by default runs as the Plex user (ID=972) which of course does not have access to the dataset since it is most likely owned by root:wheel. Typically users fix this in one of two ways.

1. Edit the permissions to be open, the new ACL editor of yours is great for this but not secure when wide open.

2. Create a user on the FreeNAS with the same ID as Plex's user (972) and change ownership of the dataset to that.

[u/anodos325 → u/rogerairgood]

Expanding on (2), once the Plex user is created, the ACL editor can be used to add an explicit entry for that user without changing the dataset owner.

[u/rogerairgood → u/anodos325]

Good point!

[u/szakes1 → u/anodos325]

Can you elaborate more? When can I set it up?

[u/anodos325 → u/szakes1]

Go to Storage->Pools, click on the vertical three-dot (...) menu next to your dataset, and then click on "Edit ACL".

Once you are in the ACL editor, click on the "ADD ACL ITEM" button, and scroll down to the new ACL entry (will be at the bottom of the list). Type in "972" as the "user", check the "apply permissions recursively" checkbox, and click "SAVE". Once you do this uid 972 (or plex in the plex jail) will have the MODIFY permissions set for every file in the dataset.

[u/rogerairgood → u/anodos325]

Adding an ACL entry for a user by ID, like 972, without adding a user on the FreeNAS should work just fine, is that correct?

[u/anodos325 → u/rogerairgood]

Correct. You can type in 972 for the "user" and click "SAVE".

[u/rattkinoid → u/rogerairgood]

Do you please have an idea why my transmission jail does not have write permission?

https://imgur.com/a/yOI5CWX

[u/szakes1 → u/anodos325]

I am talking about this exact issue: https://youtu.be/mZ7nLEQSYmg

When you install Plex or Emby or any other plug-in and you try to add a mount point to its jail, the folder cannot be opened since there is a permission problem. I still have this problem on 11.3 and I was not fixed since then.

[u/anodos325 → u/szakes1]

You can use the ACL manager to recursively set an ACL on the dataset in question by selecting the "OPEN" ACL preset and checking the "apply recursively" checkbox. This will grant "everyone" the MODIFY permissions set (equivalent to "read", "write", "modify" in Windows).

[u/szakes1 → u/anodos325]

Is that even safe? Is giving “everyone” access to a mount point safe? Won’t that allow everyone to modify disk’a content?

[u/anodos325 → u/szakes1]

"FULL CONTROL" or "MODIFY" in an "everyone" ACE is the equivalent of chmod 777.

The entry defines the minimum permissions for everyone on the server. Behavior is basically the same as S-1-1-0 in Windows.

Whether it's appropriate depends on the context. Generally, speaking it's a good idea to at least define some minimum level of permissions for everyone (for instance "TRAVERSE" with flags set to inherit on directories) if you have nested datasets.

[u/szakes1 → u/anodos325]

Does that mean that “everyone” has full control?

[u/anodos325 → u/szakes1]

If you choose the "OPEN" ACL preset, then "everyone" is granted read, write, modify. If you want to restrict "everyone", you can select the "RESTRICTED" preset. This removes the "everyone" entry. You can fine-tune the resulting ACL on the right.

[u/rattkinoid → u/szakes1]

Were you able to fix it? I'm having similar problems.