From owner-freebsd-fs@FreeBSD.ORG Tue Nov 17 22:33:51 2009 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 049C9106566B; Tue, 17 Nov 2009 22:33:51 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id C10568FC0C; Tue, 17 Nov 2009 22:33:50 +0000 (UTC) Received: from [192.168.1.4] (adsl-241-172-215.bna.bellsouth.net [74.241.172.215]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id nAHMXlVa012182 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 17 Nov 2009 17:33:48 -0500 (EST) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Emil Smolenski In-Reply-To: References: <1258390784.2303.42.camel@balrog.2hip.net> Content-Type: text/plain Organization: FreeBSD Date: Tue, 17 Nov 2009 16:33:41 -0600 Message-Id: <1258497221.2303.66.camel@balrog.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RDNS_DYNAMIC,SPF_SOFTFAIL autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: GPT boot with ZFS RAIDZ "ZFS: i/o error - all block copies unavailable" 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: Tue, 17 Nov 2009 22:33:51 -0000 On Tue, 2009-11-17 at 22:43 +0100, Emil Smolenski wrote: > On Mon, 16 Nov 2009 19:33:34 +0100, Emil Smolenski > wrote: > > >> Matt's patch only effects raidz volumes. > > Oh, I see. Maybe there is similar bug in ZFS on single disk volumes > > also? > > >>> (is this procedure of updating zfsboot correct?) > >> This should be correct for updating the first stage bootstrap code. The > >> loader (boot/loader) is actually updated during installworld. > > > > I'll try full build/installworld tomorrow. > > It, unfortunately, didn't solve this issue. 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". 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. robert. -- Robert Noland FreeBSD