Code: Select all
root@TRILLIAN:~# zfs --version
zfs-2.0.3-9
zfs-kmod-2.0.3-9
https://www.shernet.com/linux/zfs-home-directory/
The problem is the mount point, which I cannot change to /home. Before booting, I moved the /home that was created when I installed the computer to /home_bak.
The zfs pool and the home share look like this:
Code: Select all
root@TRILLIAN:~# zfs get all | grep mount
hpool mounted no -
hpool mountpoint none local
hpool canmount on local
hpool/HOME mounted yes -
hpool/HOME mountpoint /home local
hpool/HOME canmount on default
Code: Select all
root@TRILLIAN:~# zfs get all | grep overlay
hpool overlay off local
hpool/HOME overlay on local
root@TRILLIAN:~# zfs get all | grep case
hpool casesensitivity sensitive -
hpool/HOME casesensitivity sensitive
Code: Select all
Apr 02 00:23:49 TRILLIAN zfs-mount-generator: -.mount already exists. Skipping.
What is different in my configuration with respect to the one described in
https://www.shernet.com/linux/zfs-home-directory/
and other examples on the internet is that I do not have a separate dataset for each user, but one dataset called HOME where all user directories are. Moreover, I noticed that it does not matter if the zfs-load-key.service described in the link above is enabled or not. HOME finds the key file and gets mounted anyway.
If there is no way to mount the dataset directly to /home, would it be possible to replace the directory /home by a link to /HOME or may this break something I am not thinking of?
I think I remember trying to change the mount point of HOME to something different from /home and this worked. I.e., mounting HOME to /home seems to be the problem.
As always, any help is greatly appreciated.
Toquinho