HAMMER2 by default names the PFS based on the partition it was created on. And the H2 mount code will automatically add an @blah suffix according to the same metrics. But they both get confused when the mount is via the mapper and that's why the problem occurs. It might have been a bit of a stretch on my part to try to be fancy in defining the default names when they weren't otherwise being provided. I think we could detect the crypto or mapper paths and fix the defaults this way but nobody has gotten around to coding and validating it all up.
-Matt On Fri, Jan 18, 2019 at 12:38 PM Daniel Bilik <[email protected]> wrote: > Hi, Aaron. > > On Fri, 18 Jan 2019 23:02:45 +0800 > Aaron LI <[email protected]> wrote: > > > Since the HAMMER2 FS was created with '-L ROOT', it requires '@ROOT' to > > be mounted. > > Ah, that was it. Thank you for pointing out this detail. I've not expected > it could be related. > > > Another simple way to workaround your issues is use the following setting > > in /boot/loader.conf: > > vfs.root.realroot="crypt:hammer2:/dev/serno/<serial-of-disk>.s1d:rootd" > > Note the final 'd'! > > Indeed, this workaround really works. I've not examined the magic behind > it but my "ROOT" hammer2 filesystem is correctly mounted during boot with > original non-patched initrd. Thank you very much for the hint. > > -- > Daniel >
