From owner-freebsd-fs@FreeBSD.ORG Thu Sep 20 02:39:13 2007 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB61F16A421; Thu, 20 Sep 2007 02:39:13 +0000 (UTC) (envelope-from acd@acd.homelinux.org) Received: from server0.acapsecurity.com (acapsecurity.com [207.38.28.204]) by mx1.freebsd.org (Postfix) with ESMTP id 96BA513C45E; Thu, 20 Sep 2007 02:39:13 +0000 (UTC) (envelope-from acd@acd.homelinux.org) Received: from acd.homelinux.org (unknown [10.0.15.5]) by server0.acapsecurity.com (Postfix) with ESMTP id 310FB22B6E; Wed, 19 Sep 2007 19:39:12 -0700 (PDT) Received: by acd.homelinux.org (Postfix, from userid 500) id 551D43086; Wed, 19 Sep 2007 20:39:12 -0600 (MDT) From: Axel To: Adam Jacob Muller References: Date: Wed, 19 Sep 2007 20:39:11 -0600 In-Reply-To: (Adam Jacob Muller's message of "Wed\, 19 Sep 2007 20\:05\:03 -0400") Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS pool not working on boot X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Sep 2007 02:39:13 -0000 Adam Jacob Muller writes: > On Sep 19, 2007, at 6:44 PM, Axel wrote: > >> There is a file called /boot/zfs/zpool.cache that is kept in sync >> and loaded at boot time. >> >> If that's not there , e.g. by your /boot pointing to it , you're >> hosed. >> > > File is there, of note is that some of the prior reboots had been > "unintentional" reboots, so it is possible that that file was > corrupt, however, it does not seem correct for zfs to come up in a > state that shows drives as corrupted and/or unavailable. I believe I > have corrected the crashing issue, however it still does not seem > that this is the correct behavior. > > - Adam > If you have a working root outside of zfs I'd do the following: 1) Rename the zpool.cache to something else to be safe 2) Reboot, make sure that /boot/zfs points to the right location, and reimport the pools. 3) Should be fine from there on. I had sort of the same issue, the zpool.cache isn't documented too well yet; I only stumbled over it by doing a "lsmod" at the loader prompt;it's one reason root can be on zfs before hostid is set. If you setup zfs and don't have the future /boot/zfs set right it won't work because the information gets lost. With / on zfs it's crucial to have /boot point to the actual UFS boot partition and not be in your zfs / somewhere, cause that gets ignored until it's mounted. It's a good idea to keep the actual old UFS / directory around although only /boot gets used in there if you mount / from zfs. http://wiki.freebsd.org/ZFS comes in handy. And yes, I do love zfs too :-) -- Axel