From owner-freebsd-current@FreeBSD.ORG Tue Oct 23 02:24:13 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0E1BFE3D for ; Tue, 23 Oct 2012 02:24:13 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44]) by mx1.freebsd.org (Postfix) with ESMTP id D3C358FC0C for ; Tue, 23 Oct 2012 02:24:12 +0000 (UTC) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by thyme.infocus-llc.com (Postfix) with ESMTPSA id 4A88437B52F; Mon, 22 Oct 2012 21:24:11 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3Xlz1k27RdzWd7; Mon, 22 Oct 2012 21:24:10 -0500 (CDT) Date: Mon, 22 Oct 2012 21:24:10 -0500 From: "Matthew D. Fuller" To: Michael Schmiedgen Subject: Re: ZFS cache devs UNAVAIL Message-ID: <20121023022410.GA66994@over-yonder.net> References: <5085CF5E.5020500@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5085CF5E.5020500@gmx.net> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.21-fullermd.4 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.6 at thyme.infocus-llc.com X-Virus-Status: Clean Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2012 02:24:13 -0000 On Tue, Oct 23, 2012 at 12:57:34AM +0200 I heard the voice of Michael Schmiedgen, and lo! it spake thus: > > after an update to CURRENT 2012-10-17 my ZFS cache devs are marked > UAVAIL after boot. These two devs are SSD partitions that are listed > with some wired numbers (see below). Before that they were listed > fine as ada0p1 and ada1p1. I saw this after my update to 10.0-CURRENT #0 r241541: Sun Oct 14. In my case, it's ada2p2 which is the cache that comes up unavail on boot. One notable thing may be that p1 is used for ZIL, and comes up fine. NAME STATE READ WRITE CKSUM d ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada1p3 ONLINE 0 0 0 ada0p3 ONLINE 0 0 0 logs ada2p1 ONLINE 0 0 0 cache ada2p2 ONLINE 0 0 0 I notice that you also have a second partition on your drives that's part of another pool. Maybe it's related to something giving up after assigning one partition from the drive to zpool somewhere? Though in your case it's p2 that's working and p1 that's wandered off, so maybe that's not it... -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.