zroot/home canmount on local zroot/home mountpoint /home local zroot/home/vladas canmount on local zroot/home/vladas mountpoint /home/vladas inherited from zroot/home zroot/usr canmount off local zroot/usr mountpoint /usr local zroot/usr/home canmount on default zroot/usr/home mountpoint /usr/home inherited from zroot/usr
…
(Re: your post 2, it seems reasonable to summarise that the user data is not lost; that we should focus on possible explanations for failure to execute a login command.)
I don’t know enough about NomadBSD to tell whether the rollback might have had a negative impact.
My system here was locked from vladas and became read-only for admin.
Then I attempted to fix my pool — the history goes on:
2022-02-27.19:09:57 zfs set canmount=on zroot/home/vladas
2022-02-27.20:04:20 zfs set canmount=on zroot/home
2022-02-27.21:20:05 zfs set compression=off zroot/home
As far as I can remember, /home and /home/vladas were real assets from the begining, and /usr/home was always empty, with no links. Anyway, the system was locked before the mounting attempt — immediately after zfs create -v zroot/home/vladas.
Weird: I installed FreeBSD-13 on another computer, set up its user account, and got /usr/home/name for his assets, with ~/home symlink to the real user directory. Why is NomadBSD installation different?
to start the service according /etc/rc.conf — sure, but I am curious: what would happen if this service was turned off? Would that ruin the file system with an entire operating system? Or maybe just reset zpool, and eventually cancel the read-only access restriction?
Welcome back Studies did not lead to an answer, and cancellation of user’s dataset I set up by zfs destroy zroot/home/vladas did not restore access to the system. ZFS even found and destroyed my files and settings backed up in /usr/home/vladas (not linked from /home/vladas)! So I decided to reinstall NomadBSD in my laptop from USB. ZFS again, following the same dataset commands as previously: