From owner-freebsd-current@FreeBSD.ORG Fri Aug 8 19:34:47 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 26288AA8; Fri, 8 Aug 2014 19:34:47 +0000 (UTC) Received: from shxd.cx (unknown [64.201.244.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0DC802106; Fri, 8 Aug 2014 19:34:47 +0000 (UTC) Received: from 50-196-156-133-static.hfc.comcastbusiness.net ([50.196.156.133]:58821 helo=THEMADHATTER) by shxd.cx with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1XFgxB-0007gP-VY; Fri, 08 Aug 2014 02:59:18 -0700 From: To: "'Garrett Cooper'" , References: <091101cfb284$f616cbb0$e2446310$@FreeBSD.org> <1407453344.5935.3.camel@bruno> <095501cfb299$4872b090$d95811b0$@FreeBSD.org> In-Reply-To: Subject: RE: loader lszfs command Date: Fri, 8 Aug 2014 12:34:44 -0700 Message-ID: <0afa01cfb33f$cec78ed0$6c56ac70$@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQHPg+tqnJ9d5aGmqEBT91hvjPRKGwFTa5sIAYo63+AC+H56YQKEqElqm4Sf0zA= Content-Language: en-us Sender: devin@shxd.cx Cc: 'freebsd-current' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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: Fri, 08 Aug 2014 19:34:47 -0000 > -----Original Message----- > From: Garrett Cooper [mailto:yaneurabeya@gmail.com] > Sent: Thursday, August 7, 2014 5:10 PM > To: dteske@freebsd.org > Cc: Sean Bruno; freebsd-current > Subject: Re: loader lszfs command >=20 > On Thu, Aug 7, 2014 at 4:42 PM, wrote: > > > >> -----Original Message----- > >> From: Garrett Cooper [mailto:yaneurabeya@gmail.com] > >> Sent: Thursday, August 7, 2014 4:29 PM > >> To: sbruno@freebsd.org > >> Cc: dteske@freebsd.org; freebsd-current > >> Subject: Re: loader lszfs command > >> > >> Hi Devin! > >> > >> On Thu, Aug 7, 2014 at 4:15 PM, Sean Bruno > >> wrote: > >> > On Thu, 2014-08-07 at 14:17 -0700, dteske@FreeBSD.org wrote: > >> >> Hi, > >> >> > >> >> People have been pestering me to update the Forth code to = present > >> >> a menu of ZFS datasets (*cough* boot environments *cough*). > >> >> > >> >> Would love to, but existing code seems broken. > >> >> > >> >> Can *anybody* produce meaningful output from the following? > >> >> > >> >> http://svnweb.freebsd.org/base?view=3Drevision&revision=3D241284 > >> >> > >> >> All I get on every system I've tried (multiple versions, = including HEAD) > >> >> produce the following: > >> >> > >> >> OK lszfs zroot > >> >> ZFS: i/o error - all block copies unavailable > >> >> operation not permitted > >> >> > >> >> It's really hard for me to start with something that's broken. = Can > >> >> I get confirmation that this doesn't appear to be working as = intended? > >> >> If so, I'll go ahead and try to fix it, but need to confirm that = I'm ( a ) > >> >> not > >> >> crazy and ( b ) seeing the same thing everybody else is seeing. > >> > > >> > > >> > Hrm ... this seems to work for me. (fairly recent 11-current) > >> > > >> > OK lszfs zroot > >> > $MOS > >> > $FREE > >> > $ORIGIN > >> > tmp > >> > home > >> > usr > >> > var > >> > tftpboot > >> > poudriere > >> > OK > >> > >> Is the installed version you have in synch with the kernel and > >> zpool version for boot0, gptzfsboot, etc? > > > > Not sure how the kernel factors into all this, but I have a > > 10.0-RC1 system. >=20 > I was asking for information to help determine whether or not the > loader could read the zpool metadata, because it's interesting why > things worked for Sean and not for you :). No explanation as of yet, but I have successfully built a system that has working lszfs command. Took a stable/10 snapshot from July 29th and that seems to be working alright. Since it's working as expected in stable/10 currently (the furthest point away that I intend to MFC these enhancements), I'm happy to ignore the fact that my aged 10.0-RC1 machine doesn't work. --=20 Devin