From owner-freebsd-sparc64@FreeBSD.ORG Tue Jan 1 02:05:20 2013 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 148ECDBC for ; Tue, 1 Jan 2013 02:05:20 +0000 (UTC) (envelope-from cross+freebsd@distal.com) Received: from mail.distal.com (mail.distal.com [IPv6:2001:470:e24c:200::ae25]) by mx1.freebsd.org (Postfix) with ESMTP id CB6E48FC0A for ; Tue, 1 Jan 2013 02:05:19 +0000 (UTC) Received: from magrathea.distal.com (magrathea.distal.com [206.138.151.12]) (authenticated bits=0) by mail.distal.com (8.14.3/8.14.3) with ESMTP id r0125EZO000786 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 31 Dec 2012 21:05:16 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Changes to kern.geom.debugflags? From: Chris Ross In-Reply-To: <20121230032403.GA29164@pix.net> Date: Mon, 31 Dec 2012 21:05:13 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <56B28B8A-2284-421D-A666-A21F995C7640@distal.com> References: <7AA0B5D0-D49C-4D5A-8FA0-AA57C091C040@distal.com> <6A0C1005-F328-4C4C-BB83-CA463BD85127@distal.com> <20121225232507.GA47735@alchemy.franken.de> <8D01A854-97D9-4F1F-906A-7AB59BF8850B@distal.com> <6FC4189B-85FA-466F-AA00-C660E9C16367@distal.com> <20121230032403.GA29164@pix.net> To: Kurt Lidl X-Mailer: Apple Mail (2.1499) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (mail.distal.com [206.138.151.250]); Mon, 31 Dec 2012 21:05:16 -0500 (EST) Cc: freebsd-sparc64@freebsd.org, Marius Strobl X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jan 2013 02:05:20 -0000 On Dec 29, 2012, at 10:24 PM, Kurt Lidl wrote: > On Sat, Dec 29, 2012 at 03:01:55PM -0500, Chris Ross wrote: >> I'm going to guess this is a problem with dnode->dn_datablkszsec. >> Has anything changed recently in zfs_fmtdev, or more likely = zfs_get_root() >> or objset_get_dnode(), which is the callchain right before = dnode_read() ? >=20 > Well, there has been a big set of bugfixes integrated into zfs since > the 9.1-RELEASE, particularly revision r243674: >=20 > = ------------------------------------------------------------------------ > r243674 | mm | 2012-11-29 09:05:04 -0500 (Thu, 29 Nov 2012) | 223 = lines >=20 > Merge ZFS feature flags support and related bugfixes: > 236884, 237001, 237119, 237458, 237972, 238113, 238391, 238422, = 238926, > 238950, 238951, 239389, 239394, 239620, 239774, 239953, 239958, = 239967, > 239968, 240063, 240133, 240153, 240303, 240345, 240415, 240955, = 241655, > 243014, 243505, 243506 >=20 > [ long, long description elided ] > = ------------------------------------------------------------------------ >=20 > However, I think it's more likely that this revision, particularly > r239068 that is the probably cause of the issue you are seeing. > I don't particularly care for giant patches like this, where > trying to figure out exactly what piece of what patch did what, > but that's the way it goes. >=20 > So, to answer your question, "Yes, lots of stuff has changed recently > with ZFS". Okay. Well, I tried building stable/9 at revision 243673, which = didn't work, and then 243242, which also failed in the same way. So, it may be something = earlier than the suggested (if I'm reading your email correctly, and 243243 is = where the rev you mentioned was integrated to stable/9.) Thanks much for the pointers! I'll try to take a look at some of the = underlying changes, and see if anything looks more relevant. - Chris