I have been running an Unraid server for about 6 months for docker, vms, backups media server, etc.,
Now I’m setting up a second Unraid server using ZFS and more storage. The plan is to put most of the storage on the ZFS array allowing me to do snapshots and other fun things. I want to put docker containers, vm’s and backups, etc on ZFS and not the native Unraid array.
I’m using a 1TB sata drive as the Unraid storage, no parity or cache or anything for now while I’m testing.
I have a RaidZ array configured, using an LSI SAS2308 and 8x 4TB SAS drives.
I installed the ZFS Plugins for Unraid. Created a zpool and some datasets.
From the console I can access this storage. I did a chown -R nobody:users on /mnt/disks/zfs-sas so the ownership should be good.
SpaceInvader One suggests making a symlink from my dataset to /mnt/user/datasetmountpoint
ie., ln -s /mnt/disks/zfs-sas/isos /mnt/user/isos
This seems to work fine, but the log gets spammed with this error:
Jun 22 00:20:13 unraid1 emhttpd: error: share_luks_status, 6151: Operation not supported (95): getxattr: /mnt/user/isos
So I try using smb-extra configuration section to share the datasets.
ie.,
[appdata]
path=/mnt/disks/zfs-sas/appdata
valid users = root,sbrewer
write list = root,sbrewer
While I can now see the shares remotely, they aren’t visible locally, and I’m not sure why not.
I can’t use them to for paths in Docker config or VM-manager config.
If I do this using the symlinks instead, then I can use them and it seems to work. Except for the errors.
Should I be able to do this for Docker and VM’s?
What am I missing?
