From owner-freebsd-sparc64@FreeBSD.ORG  Sat Jan  5 00:38:16 2013
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 4EACE4A1
 for <freebsd-sparc64@freebsd.org>; Sat,  5 Jan 2013 00:38:16 +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 F3B77D6
 for <freebsd-sparc64@freebsd.org>; Sat,  5 Jan 2013 00:38:15 +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 r050cA6s019709
 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
 Fri, 4 Jan 2013 19:38:11 -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 <cross+freebsd@distal.com>
In-Reply-To: <20130104234616.GA37999@alchemy.franken.de>
Date: Fri, 4 Jan 2013 19:38:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A53D7D35-5C0D-43B7-BCDF-5156564C4B45@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>
 <A947C892-5379-4F70-BFA0-0A7AB94DF0C6@distal.com>
 <6FC4189B-85FA-466F-AA00-C660E9C16367@distal.com>
 <20121230032403.GA29164@pix.net>
 <56B28B8A-2284-421D-A666-A21F995C7640@distal.com>
 <EEB60849-3192-46E2-8626-EC6824182515@distal.com>
 <20130104234616.GA37999@alchemy.franken.de>
To: Marius Strobl <marius@alchemy.franken.de>
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]); Fri, 04 Jan 2013 19:38:11 -0500 (EST)
Cc: freebsd-sparc64@freebsd.org, Kurt Lidl <lidl@pix.net>
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-sparc64>, 
 <mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
 <mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 00:38:16 -0000


On Jan 4, 2013, at 18:46 , Marius Strobl <marius@alchemy.franken.de> =
wrote:
> On Thu, Jan 03, 2013 at 11:27:44PM -0500, Chris Ross wrote:
>>  So, now that we're past the holiday madness, and I haven't heard =
anything back
>> on this is there some other group or list I should ask the questions =
of ZFS internals
>> to figure out why the sparc64 MD boot loader code is seeing a =
dn_datablkszsec
>> of 0, and what it should be set to?
>>=20
>>  Thanks.  I'm happy to compose another message to include people who =
might
>> be able to help.  I'm out of my "comfort zone" in ZFS.
>>=20
>=20
> The most straightforward way is to identify the commit that broke
> it via a binary search and email the corresponding commit.

  And while that would take time, I'm happy to do it, but it's hard =
given all the
merges which include many other revisions from trunk.

  I was just hoping someone that knew what dn_datablkszsec is and/or
should be would be able to help identify the fix before trying to figure =
out
what broke it in the first place.

                      - Chris