From owner-freebsd-questions@FreeBSD.ORG Tue Apr 16 04:49:36 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 76C3836B for ; Tue, 16 Apr 2013 04:49:36 +0000 (UTC) (envelope-from zaphod@berentweb.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 5BBC0CCE for ; Tue, 16 Apr 2013 04:49:35 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1URxph-0000SG-2m for freebsd-questions@freebsd.org; Mon, 15 Apr 2013 21:49:29 -0700 Date: Mon, 15 Apr 2013 21:49:29 -0700 (PDT) From: Beeblebrox To: freebsd-questions@freebsd.org Message-ID: <1366087768996-5804167.post@n5.nabble.com> In-Reply-To: References: Subject: ZFS mounting failed with error 2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Apr 2013 04:49:36 -0000 >> one thing I'm not sure about is that some people create a dataset root but that actually mounts at / (and not /root) and some just create others mount points directly on the zpool You can do this either way. A ZFS dataset is created at the same time and with the same name as the zpool. You can use the zpool-named-dataset as root without any problem. As I recall, the separate root dataset was a work-around for some old problem, so it is not necessary any longer. That said, you can place and name the zfs root dataset anywhere you want, as long as you have the 'vfs.root.mountfrom=' path set correctly. In your example, it is set correctly. Now as to why you cannot boot - from my experience, the problem is your last command: '# zpool export tank' will leave the pool in an exported state, and when the system tries to boot, it will not be able to locate the zpool because the pool is in exportland. The solution is different. After you are finished with all your settings you should # zfs umount -a (unmount all tank & child datasets in /mnt) # zfs set mountpoint=/ tank # reboot At step 2, dataset tank should not try to re-mount its self and remain un-mounted. The older versions of ZFS did not behave this way and would immediately mount the zpool on root. If this happens, you have to hard-reset and such because the system will freeze up. If all goes well, before reboot you can also check (zfs get all tank) and make sure that canmount=on is set for tank. The best zfs guide is FreeBSD's own docs: https://wiki.freebsd.org/RootOnZFS ----- 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 & xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-mounting-failed-with-error-2-tp5802786p5804167.html Sent from the freebsd-questions mailing list archive at Nabble.com.