Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Jan 2018 11:05:45 +0700
From:      Victor Sudakov <vas@mpeks.tomsk.su>
To:        Trond Endrest?l <Trond.Endrestol@fagskolen.gjovik.no>
Cc:        FreeBSD questions <freebsd-questions@freebsd.org>
Subject:   Re: Dualboot and ZFS
Message-ID:  <20180119040545.GA44997@admin.sibptus.transneft.ru>
In-Reply-To: <alpine.BSF.2.21.1801180938440.69908@mail.fig.ol.no>
References:  <20180115125241.GB60956@admin.sibptus.transneft.ru> <VI1PR02MB1200C7F0066F361E60A6CBEDF6EB0@VI1PR02MB1200.eurprd02.prod.outlook.com> <20180115144747.GA65526@admin.sibptus.transneft.ru> <VI1PR02MB120018D174817F8FFB2981D5F6EB0@VI1PR02MB1200.eurprd02.prod.outlook.com> <20180115151526.GA66342@admin.sibptus.transneft.ru> <a7920f859b666cff48f4f73ee1b2f954@dweimer.net> <20180116034929.GB89443@admin.sibptus.transneft.ru> <alpine.BSF.2.21.1801160934560.69908@mail.fig.ol.no> <20180118051423.GA94227@admin.sibptus.transneft.ru> <alpine.BSF.2.21.1801180938440.69908@mail.fig.ol.no>

next in thread | previous in thread | raw e-mail | index | archive | help
Trond Endrest?l wrote:

[dd]

> 
> The key is to place some of the bootcode in the boot block of the 
> disklabel and the remainder in the boot block of the zpool.

OK, I'm experimenting in bhyve anyway, so I can put all that bootblock
hassle for later. bhyve does not use the bootblocks anyway.

There is another issue that I don't understand. After creating the
root zpool like the howtos (and you) recommend, I get a bootable
system, but for some reason all the children datasets of the BE
are not mounted after boot. Like this:

root@test1:~ # mount
zroot3/ROOT/default on / (zfs, local, nfsv4acls)
devfs on /dev (devfs, local, multilabel)
root@test1:~ #

root@test1:~ # zfs list -o name,used,avail,refer,mountpoint,canmount,mounted
NAME                  USED  AVAIL  REFER  MOUNTPOINT  CANMOUNT  MOUNTED
zroot3               1.05G  6.64G    23K  /zroot3           on       no
zroot3/ROOT          1.05G  6.64G    23K  none              on       no
zroot3/ROOT/default  1.05G  6.64G  1.05G  /                 on      yes
zroot3/tmp             24K  6.64G    24K  /tmp              on       no
zroot3/usr             92K  6.64G    23K  /usr             off       no
zroot3/usr/home        23K  6.64G    23K  /usr/home         on       no
zroot3/usr/ports       23K  6.64G    23K  /usr/ports        on       no
zroot3/usr/src         23K  6.64G    23K  /usr/src          on       no
zroot3/var            266K  6.64G    23K  /var             off       no
zroot3/var/audit       23K  6.64G    23K  /var/audit        on       no
zroot3/var/crash     23.5K  6.64G  23.5K  /var/crash        on       no
zroot3/var/log        150K  6.64G   150K  /var/log          on       no
zroot3/var/mail        23K  6.64G    23K  /var/mail         on       no
zroot3/var/tmp         24K  6.64G    24K  /var/tmp          on       no
root@test1:~ #

What have I forgotten when creating the pools?
This is how I did it: http://termbin.com/awuy
Based on https://wiki.freebsd.org/RootOnZFS/ZFSBootPartition

I can mount all those datasets manually though: 

root@test1:~ # zfs mount zroot3/var/mail
root@test1:~ # mount
zroot3/ROOT/default on / (zfs, local, nfsv4acls)
devfs on /dev (devfs, local, multilabel)
zroot3/var/mail on /var/mail (zfs, local, nfsv4acls)
root@test1:~ #

But for some reason it's not happening on boot.

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
AS43859



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180119040545.GA44997>