I am looking at moving back to UNRAID now that it supports ZFS. I switched because I could not achieve high enough read speeds for LTO6 backups. I see that UNRAID is very picky about pool names but easy enough to change. My problem is shares. Standard practice is not to use the root dataset for shares, but with a test pool I created I can not figure out a way to assign a share to a child dataset. All my Truenas pools are setup with child dataset shares. Will I be able to import them into UNRAID?

thanks

4 hours ago, roberth58 said:

Will I be able to import them into UNRAID?

Yes, but if you want to create more you will need to use the CLI or the ZFS master plugin for now.

I have the ZFS master plugin and it will let you create child datasets as will the CLI, my problem is how to create a share on a child dataset. If you "add share" in the gui the primary storage choice does not let you pick a child dataset. Can you do this from the CLI? If you can use the CLI for this could you point me at a page showing this.

1 hour ago, roberth58 said:

my problem is how to create a share on a child dataset

You can't, you can have child datasets, but with Unraid, only top level folders/datasets can be a share.

So what you meant when you said I can import my pools from Truesnas is that they will import but be completely useless until I destroy my dataset structure and move all my data from every dataset into a share/folder at the top level. So no different recordsize for different types of data. Also changing all the docker volumes. Is there a reason that UNRAID cant use standard ZFS structure? Also why support child datasets if you cant use them? I really wanted to go back to UNRAID but this current ZFS implementation doesn't seem ready for primetime.

You can still use the chid datasets under a main share, but if you want to have them as individual shares, you would need to move them to top-level datasets.

Are you saying that I can kep my child datasets with different recordsizes but to access them i just treat them as a folder. Say I have a top level dataset named storage and child datasets called TV and Movies. In Truenas I have 2 shares TV and Movies, in UNRAID I could just use storage/TV and storage/Movies instead. I think I can make this work, thanks. I really didn't want to change my data structure so I could easily switch back to Trunas if needed. I just have to think like trashguides as far as file and folder structure.

Yes, that's should work fine, you just won't be able to have specific share settings for the child datasets, but their other settings like recordsize, etc, would still apply.

Info for anyone else importing child datasets. UNRAID sets owner to nobody for the top level, but child datasets are root. I could not access from Windows until I did a change owner on the datasets. This is not instantaneous for 140TB but it will finish eventually :)