It might be also a result of the bogus mount.zfs, which requires POSIX incorrect arguments but honors POSIXLY_CORRECT env var!
Had a similar zfs mount order problem with a rpool/local/home/{A,B,C} tree (was created using -p option) ...
It might be also a result of the bogus mount.zfs, which requires POSIX incorrect arguments but honors POSIXLY_CORRECT env var!
Had a similar zfs mount order problem with a rpool/local/ home/{A, B,C} tree (was created using -p option) ...