Congratulations on integrating ZFS!
*** MY BAD *** Creating a single disk share actually makes a datastore *****
I would like to create a ZFS-only shares on the array and have a separate datastore for each share to enable replication and snapshots. While going through the release notes, I came across the following information: "Top-level user shares in a ZFS pool are created as datasets instead of ordinary directories." However, I haven't found an official way to achieve this for a single ZFS drive within the array through the settings.
Manually, it is easy to accomplish, but I wanted to think aloud and see if anyone has any insights into potential issues with my strategy in unRAID or if there are alternative approaches that align better with the "Out of the box - unRAID way". In my understanding, this approach should work, but I am unsure if I might unintentionally disrupt any underlying mechanisms in unRAID by manually creating the datasets.
Here's what I have done so far:
Converted disk 15 to ZFS.
Manually created disk15/Nextcloud.
Configured the included disk to only include disk 15.
Migrated my existing data to disk 15.
So far so good, but please let me know if you have any suggestions on a better strategy and/or if there are any potential concerns with my current setup.
PS I guess Exclusive access is not relevant here since the folder is on the array, not a zfs pool.