From owner-freebsd-fs@freebsd.org  Wed Aug  3 13:34:14 2016
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 3CCB6BACC1A
 for <freebsd-fs@mailman.ysv.freebsd.org>; Wed,  3 Aug 2016 13:34:14 +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 213AC18E3
 for <freebsd-fs@FreeBSD.org>; Wed,  3 Aug 2016 13:34:14 +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 u73DYDLk032102
 for <freebsd-fs@FreeBSD.org>; Wed, 3 Aug 2016 13:34:13 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 209096] zfsroot bricked on 10.3-RELEASE
Date: Wed, 03 Aug 2016 13:34:14 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: misc
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords: needs-patch, needs-qa
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: karl@denninger.net
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: mfc-stable10? mfc-stable11?
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-209096-3630-UdLlkhRX7Q@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209096-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-209096-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.22
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: Wed, 03 Aug 2016 13:34:14 -0000

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

karl@denninger.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |karl@denninger.net

--- Comment #29 from karl@denninger.net ---
(In reply to Daniel Ylitalo from comment #28)

Not really if the disk is > 2Tb.  On original install the kernel was likely=
 in
the first 2Tb, but once you start filling the disk the new write of the new
/boot/kernel directory may go into blocks beyond that boundary, and now it's
unreadable at boot time.

This can happen on a UFS disk too.... not sure if that's what's going on but
it's certainly possible.

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