From owner-freebsd-current@freebsd.org Fri Dec 15 23:37:12 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B736E8F6A6 for ; Fri, 15 Dec 2017 23:37:12 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C544D69F36 for ; Fri, 15 Dec 2017 23:37:11 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id r6so21843123itr.3 for ; Fri, 15 Dec 2017 15:37:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=xpMC3BMXSRA+1CsSLheafS2cRGg6hlPhr8c64+j7u7U=; b=xDYyfhP2xa7oeDCGQkHIemz9jZIIKqHjihbN/7YLNKWCtNnEGYoHW490yUTFaR85nX /fFZ7UhqjzHO8qeMOwSkhIgz+C3kBMX0Ip6KtZvWNmkeNvlUd+3k6q+gWAfMnqZECd+R XrINAhhCIBC30hcUsBOlpAwwL1SqNSdrA2naLJ1u1ANAmXkcp3YZNSozdxco4+MP0oGQ KgcWgcGvvU+TMv2yjQRse4kqoKKtM6weuOOBm219obN9HwDj/4yTYfeN9rMN7xb/2Fi/ XQ+385BE5nLmvkHYju27WQ528X8tQcyh2DGXSlJn9PMHbh2ThIFnKZuXsolhemuYot1D 5xcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=xpMC3BMXSRA+1CsSLheafS2cRGg6hlPhr8c64+j7u7U=; b=m/k8rrK4BiMDc24Jayqu9zYolNZn5rGEmOShEEQTOuYiIFCuohE6hupU7PCIf8NQq2 x8JnlFhj58uILYs0Ja7sJ2xvSSTpNFvobfhubAu5v/dci19BhO3HJYQtyWVehS/unB3J GdAid5bAt9StBPaFwRe5YACXjslol57bm5lowvRI9lBUqoyGp0IT9kqIeShaL/G2jbdd z+0K/yJfRfF8CS/89S54yiefiTYV6zAjuN4uXt7ASgL5OrPqigPFO6KaX72qaPSZUtLb yBrbetqqLhPzDRD1n36T4rT29KmLgVuVCjeeqxYE3qINzHVWhM2Iygq+DopxrioPDPRk rLtg== X-Gm-Message-State: AKGB3mJiASuxW19SMjCweDwbeomClFSWcbimvWDJtIXCdxbD/4ir0NGv T7V0gbhBXdBYk39BH6q8wH/QawUDeit1X4Vz8lBaYg== X-Google-Smtp-Source: ACJfBoun0xdrirf3LL20BKnS/A4W+ieDJVTZeEX/omhWyngoVeDrxoIJpgn87jxHN0YyOeF7X7HkrrEDKGlxslbfddQ= X-Received: by 10.36.133.135 with SMTP id r129mr11730035itd.69.1513381031022; Fri, 15 Dec 2017 15:37:11 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Fri, 15 Dec 2017 15:37:10 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: From: Warner Losh Date: Fri, 15 Dec 2017 16:37:10 -0700 X-Google-Sender-Auth: 62jHFTDiIiyOKzwPXgvUYFtG_P4 Message-ID: Subject: Re: GPTZFSBOOT in Current r326622 has problems To: lausts@acm.org Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 15 Dec 2017 23:37:12 -0000 On Wed, Dec 6, 2017 at 8:54 AM, Warner Losh wrote: > > > On Wed, Dec 6, 2017 at 8:35 AM, Thomas Laus wrote: > >> Group: >> >> I updated my amd64 computer today to r326622 and copied the >> /boot/gptzfsboot file to each of my ZFS hard drives p1 partition. The >> BTX loader stopped and could not load. This rendered my system >> 'un-bootable'. I copied this file from an earlier live filesystem CD, >> which restored my computer and enabled me to boot. >> > > Any chance you can bisect when this happened? I think I'll need more > details to see what happened. What was your old loader that world based on? > I believe that these issues have been corrected in r326888. My refactoring to make it easier to bring in the lua boot loader in r326593 (after breaking the build in r326584 accidentally) uncovered some latent subtle ordering issues. This cause GELI-enabled (but not even using) ZFS boot loaders to fail. This was related to an odd interaction between zfs and geli implementation files in gptzfsboot (and zfsboot) which caused us to have two different implementations of malloc, with all the fun you'd expect when the second one got called. If you have issues after r326888, please let me know. Warner