Exclusive shares are also indicated on the Shares page. (An additional check is made to ensure the share also does not exist on any other volumes.) There is a new status flag, 'Exclusive access' which is set to 'Yes' when a bind-mount is in place and, 'No' otherwise. If Primary storage for a share is a pool and Secondary storage is set to "none", then we can set up a bind-mount in /mnt/user/ directly to the pool share directory. When there is Secondary storage configured for a share the "Mover action" setting becomes enabled, letting the user select the transfer direction of the mover: For example, since a share is created as a ZFS dataset, it could have a different compression setting than the parent pool if we need to implement this. When a ZFS named pool is selected for either Primary or Secondary storage, there are no additional settings at this time but there could be some in the future. When a btrfs named pool is selected for either Primary or Secondary storage, an additional setting slides in: When "Array" is selected for either Primary or Secondary storage, a set of additional settings slide in: If Primary storage is "Array", then only "none" appears as an option If Primary storage is a pool name, then the only options are "none" and "Array" The "none" option is included, ie, Secondary storage is optional "Array" can be selected (meaning the unRAID array) The "none" option is omitted, ie, Primary storage must be selected If Primary storage is below the Minimum Free Space setting then new files and folders will be created in Secondary storage, if configured.Įach input presents a drop-down which lists "array", "none", and each named pool as a selection according to some configuration rules: Primary storage is where new files/folders are created. This feature is primarily aimed at maximizing I/O for large fast ZFS pools accessed via a fast networkĬonfiguring the storage options for a share is specified using two inputs: In this case we set up a bind-mount, bypassing the FUSE-based User Share file system. This is simply a share where all the data exists in a single named pool. The old concept of main storage being the unRAID array with an optional "Cache" is confusing to many new users, especially since cache has a specific meaning in ZFS.Īlso outlined below, we introduced the concept of an exclusive share. We decided to introduce this change now because of increased interest in Unraid OS now that ZFS is supported. The concept outlined below is something we planned on introducing in the Unraid OS 6.13 cycle. Normally such a change would not happen in an -rc series however, in this case the under-the-hood coding was minimal. New in this release is a conceptual change in the way storage is assigned to shares. Please refer to the 6.12.0-rc1 topic for a general overview.įixes bug in bind-mount when share names contain spaces.
0 Comments
Leave a Reply. |