Then please share the output of the
zfs get mounted,canmount data data/home
command which I asked for earlier.
Seems your issue doesn't necessarily evolve around
/home but around the ZFS
data dataset which somehow cannot be accessed. That's a different scenario than you initially told us about. Because now I don't understand where Samba comes into play (if you're only using it to share data then let's ignore that for now though).
To get answers on a tech forum it's vital that you're as clear and detailed as possible. Because without that information we can't help you. It might be obvious for you that "
I cannot access /home" also implies that there could be an issue with your other dataset, but how are we supposed to know about
data if you're not telling us about it? And with all due respect but changing the story as the community tries to gather all the information needed to find the cause of your problems can be demotivating to some.
Anyway, right now I think that your problem might be caused by
data which doesn't mount cleanly during boot, and I suspect that the cause lies with the
canmount property for
zsyst/ROOT/default which is set to
false in order to cater to
sysutils/beadm. A setup I'm
definitely not a fan off because it causes a lot of collateral damage.
It is just a wild theory but I think that because
/ isn't automatically mounted during the main boot phase it causes a problem for
data as well. As a result you only see the mountpoints but not the actual data.
The reason I say this is because I know that a scenario with two or more pools can work without any problems:
Code:
breve:/home/peter $ zpool list
NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
zdata 464G 131G 333G - 27% 28% 1.00x ONLINE -
zroot 33.8G 19.6G 14.1G - 60% 58% 1.00x ONLINE -
breve:/home/peter $ zfs list zroot zdata
NAME USED AVAIL REFER MOUNTPOINT
zdata 131G 318G 104K /opt
zroot 24.7G 7.96G 6.61G /
Of course this ZFS installation wasn't set up by the (IMO braindead) default installer.