From owner-freebsd-fs@freebsd.org  Thu Aug 10 15:29:01 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@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 68FDADD5A8C
 for <freebsd-fs@mailman.ysv.freebsd.org>; Thu, 10 Aug 2017 15:29:01 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 57E9664DA3
 for <freebsd-fs@FreeBSD.org>; Thu, 10 Aug 2017 15:29:01 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7AFT0TV098726
 for <freebsd-fs@FreeBSD.org>; Thu, 10 Aug 2017 15:29:01 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 221077] Boot from ZFS fails following freebsd-update
Date: Thu, 10 Aug 2017 15:29:01 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords: regression
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: bacon4000@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-221077-3630-ponDGCPMmV@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221077-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-221077-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Aug 2017 15:29:01 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221077

--- Comment #7 from Jason Bacon <bacon4000@gmail.com> ---

The problem occurred when booting from ZFS.

Since I had to get this system back online and reliable ASAP, I backed it up
and reinstalled with a UFS boot partition.

I had a similar issue twice on another system booting from ZFS a couple yea=
rs
ago, but it was easily worked around by recreating the contents of /boot.  =
That
little hack didn't work this time.

As I mentioned, I will continue to boot from ZFS on some of my development
systems and "hope" the problem returns so we can properly diagnose it.

I'll add that the problem seems to occur after particularly heavy writes to=
 the
pool, if 3 times qualifies as a pattern.

In this case, I had just installed a few hundred ports from source.

In the previous case, I had done an rsync backup to the system from another
server I was upgrading.

--=20
You are receiving this mail because:
You are the assignee for the bug.=