Date: Sun, 16 Jan 2011 12:00:29 +0100 From: =?iso-8859-1?Q?Marcus_M=FCller?= <znek@mulle-kybernetik.com> To: "Ronald Klop" <ronald-freebsd8@klop.yi.org> Cc: freebsd-fs@freebsd.org Subject: Re: Multiple ZFS pools and booting Message-ID: <161324AD-8882-4858-9ABF-3677F708D00B@mulle-kybernetik.com> In-Reply-To: <op.vpbp65xp8527sy@pinky> References: <37C1E643-C7A9-4061-8316-281819AC947E@mulle-kybernetik.com> <op.vpbp65xp8527sy@pinky>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Ronald, > Shouldn't you set the boot device in /boot/loader.conf? > I have this line: > vfs.root.mountfrom=3D"zfs:zroot" that's just about setting the root partition (what get's mounted as = "/"). Interestingly, its mountpoint property doesn't have to be "/", = thus you can have any ZFS filesystem mounted as root (given, that its = contents are suitable for this). My question was more or less from which pool /boot/loader.conf is read = from initially. I suspect that the order of pools on a single disk is = sequentially read, starting from the first partition. In the meantime I've created a virtual machine with the same setup as my = server. I can confirm that any exported or destroyed pools are not = tested, which is as I expected. The only question I have left now is if there is any option/property to = skip an imported pool from being used as a pool to boot from? Cheers, Marcus --=20 Marcus Mueller . . . crack-admin/coder ;-) Mulle kybernetiK . http://www.mulle-kybernetik.com Current projects: http://www.mulle-kybernetik.com/znek/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?161324AD-8882-4858-9ABF-3677F708D00B>