Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Sep 2013 15:23:00 -0400 (EDT)
From:      "Lawrence K. Chen, P.Eng." <lkchen@ksu.edu>
To:        Mark Martinec <Mark.Martinec+freebsd@ijs.si>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: zfs_enable vs zfs_load in loader.conf (but neither works)
Message-ID:  <99471506.80369991.1379013780610.JavaMail.root@k-state.edu>
In-Reply-To: <201309091956.53759.Mark.Martinec%2Bfreebsd@ijs.si>

next in thread | previous in thread | raw e-mail | index | archive | help


----- Original Message -----
> Adam Nowacki writes:
> > zfs set mountpoint=legacy data/root
> >   together with
> > zpool set bootfs=data/root data
> > 
> > setting vfs.root.mountfrom is not required - this is handled by the
> > bootfs property, as is listing / in fstab
> 
> So what happens if multiple pools each have their bootfs set?
> 
>   Mark
> _______________________________________________

Unless things have changed...the boot loader only looks at the first freebsd-zfs partition on the disk its booting.

Tripped me up once because originally I had a swap partition before my root zpool, but switched to in pool swap so I thought I would just turn the swap partition into an extra zpool.  Had hoped using zfs would fix the random disk errors in swap bringing me down, ended up keeping it swap but gmirror'd.  Later found I had a bad DIMM and a flaky controller....

Lawrence



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