From owner-freebsd-current@FreeBSD.ORG Wed Nov 18 00:17:22 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5DCA1065676; Wed, 18 Nov 2009 00:17:22 +0000 (UTC) (envelope-from ambsd@raisa.eu.org) Received: from raisa.eu.org (raisa.eu.org [83.17.178.202]) by mx1.freebsd.org (Postfix) with ESMTP id 7D0278FC0A; Wed, 18 Nov 2009 00:17:22 +0000 (UTC) Received: from bolt.zol (62-121-98-25.home.aster.pl [62.121.98.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by raisa.eu.org (Postfix) with ESMTP id 10BFE66D; Wed, 18 Nov 2009 01:21:28 +0100 (CET) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Robert Noland" References: <1258390784.2303.42.camel@balrog.2hip.net> <1258497221.2303.66.camel@balrog.2hip.net> Date: Wed, 18 Nov 2009 01:17:20 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Emil Smolenski" Message-ID: In-Reply-To: <1258497221.2303.66.camel@balrog.2hip.net> User-Agent: Opera Mail/10.01 (FreeBSD) Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Boot with ZFS on single disk: "ZFS: i/o error - all block copies unavailable" [was: Re: GPT boot with ZFS RAIDZ "ZFS: i/o error - all block copies unavailable"] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 18 Nov 2009 00:17:22 -0000 On Tue, 17 Nov 2009 23:33:41 +0100, Robert Noland wrote: >> Should I file a PR? I would >> like to help in debugging it (however my skills in low-level C aren't >> strong enough to do it on my own). > Ok, the first thing I would like to see is "zdb -uuu". # zdb -uuu pgpool Segmentation fault: 11 (core dumped) # zdb pgpool version=13 name='pgpool' state=0 txg=439808 pool_guid=3920915583055727184 hostid=1642959122 hostname='unset' vdev_tree type='root' id=0 guid=3920915583055727184 children[0] type='disk' id=0 guid=5859773264564918193 path='/dev/da0' whole_disk=0 metaslab_array=23 metaslab_shift=35 ashift=9 asize=4500799356928 is_log=0 DTL=260 > I don't see an > obvious issue with single disk reads. My own setup uses 2 x 1TB > currently. Failing to read the MOS is basically the first read attempt > from the pool, in fact it is the read that attempts to mount the pool. -- am