From owner-freebsd-fs@freebsd.org  Wed Aug  3 14:47:54 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 3E913BAE257
 for <freebsd-fs@mailman.ysv.freebsd.org>; Wed,  3 Aug 2016 14:47:54 +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 2E2711690
 for <freebsd-fs@FreeBSD.org>; Wed,  3 Aug 2016 14:47:54 +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 u73ElrQh020197
 for <freebsd-fs@FreeBSD.org>; Wed, 3 Aug 2016 14:47:54 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 14:47:53 +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: 
Message-ID: <bug-209096-3630-lFiBw2o9CW@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 14:47:54 -0000

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

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

This has ALWAYS been dangerous on a disk that is >2Tb; the solution is to p=
lace
the boot (or boot/root, if they're on the same filesystem) within the first=
 2Tb
and do *not* allow the size of that filesystem to cross the 2Tb boundary.  =
This
is an especially nasty problem because it appears that all is ok and is for=
 a
while, right up until the system starts allocating space beyond the boundary
when you do an update... then you are suddenly hosed as the machine will not
boot.

It is safe to have root/boot on a disk larger than 2Tb, but *not* to allow =
the
size of that filesystem to extend across that boundary.

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