The pool has 12 datasets, some compressed, some encrypted. They are mostly at their default mountpoints - e.g. /Volumes/nas/backup/ for the dataset called "backup". For local access on the Mac Mini everything works fine.
When accessing the server from other Macs I have two problems:
- when I mount the backup dataset, it gets mounted at /Volumes/backup/, but I'd like it to be mounted at /Volumes/nas/backup/ for consistency (so scripts don't need to worry if they are running on the server or on a client machine).
- I was hoping that I could mount the datapool, and then have the datasets accessible under that, but if I try to mount the datapool, which I can see as a shared volume as "nas", it crashes Finder (spinning wheel of eternity) so badly that I have to reboot the Mac. I get the same behaviour on both an Intel 10.15 mac, and an M1 macos 12 mac.
I could work around the first issue, by setting the local mountpoint of each dataset to be directly under /Volumes/, i.e. /Volumes/backup/ in this case - though with 12 of them it would be neater to have them contained under a directory.
The crash is more problematic - not good that accidentally trying to mount the datapool share requires a reboot.
Should it be possible to mount the datapool share directly, and access the datasets under that pool? If not, can I stop the pool showing as a share so I don't accidentally crash Finder and have to reboot?
Thanks,
mark.