From owner-freebsd-bugs@freebsd.org  Fri Jul 28 15:18:14 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 64960DC80CB
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Fri, 28 Jul 2017 15:18: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 526F16496B
 for <freebsd-bugs@FreeBSD.org>; Fri, 28 Jul 2017 15:18: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 v6SFIEmG092244
 for <freebsd-bugs@FreeBSD.org>; Fri, 28 Jul 2017 15:18:14 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 221067] vfs.root.mountfrom.options="ro" did not take effect for
 a zfs root filesystem
Date: Fri, 28 Jul 2017 15:18:14 +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: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: allanjude@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-221067-8-Utfj1HqcbO@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221067-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-221067-8@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-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 15:18:14 -0000

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

--- Comment #1 from Allan Jude <allanjude@FreeBSD.org> ---
/ gets mounted read-only in single user mode, with a mount flag (so the poo=
l is
not imported read-only, but the filesystem is mounted read only), and then =
it
is upgraded to readwrite during the switch to multiuser mode.

Are you wanting the entire pool to be imported read only? Or just the one
dataset to be mounted readonly?

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