From owner-freebsd-fs@freebsd.org  Fri Dec  4 13:51:38 2015
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 17991A419A2
 for <freebsd-fs@mailman.ysv.freebsd.org>; Fri,  4 Dec 2015 13:51:38 +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 03A7F10FB
 for <freebsd-fs@FreeBSD.org>; Fri,  4 Dec 2015 13:51:38 +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 tB4DpbCh040560
 for <freebsd-fs@FreeBSD.org>; Fri, 4 Dec 2015 13:51:37 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 204976] zfs root fails to boot raidz1 raidz2 raidz3
Date: Fri, 04 Dec 2015 13:51:38 +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: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: fk@fabiankeil.de
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-204976-3630-RRzXeIl6B2@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204976-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-204976-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.20
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: Fri, 04 Dec 2015 13:51:38 -0000

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

Fabian Keil <fk@fabiankeil.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fk@fabiankeil.de

--- Comment #1 from Fabian Keil <fk@fabiankeil.de> ---
I'm not sure I understand you correctly, but I would not expect
the installer to modify devices that weren't selected as install
devices.

I also would not expect the system to boot reliably if some
of the disks (that were not modified during the installation)
contain invalid boot code.

It could be argued that the installer should warn about the
issue but that's not really a ZFS-specific problem.

To get the attention from the people working on the installer
it might help to adjust the subject and to clarify the report.

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