From owner-freebsd-fs@FreeBSD.ORG  Wed Jan 28 15:06:35 2015
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 0E076FB5
 for <freebsd-fs@FreeBSD.org>; Wed, 28 Jan 2015 15:06:35 +0000 (UTC)
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 E91BBF0C
 for <freebsd-fs@FreeBSD.org>; Wed, 28 Jan 2015 15:06:34 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t0SF6Y8U060578
 for <freebsd-fs@FreeBSD.org>; Wed, 28 Jan 2015 15:06:34 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 168158] [zfs] incorrect parsing of sharenfs options in zfs
 (fsshare.c)
Date: Wed, 28 Jan 2015 15:06:35 +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: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: Robert.nr1@gmail.com
X-Bugzilla-Status: In Progress
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-168158-3630-l3agk0jsVW@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-168158-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-168158-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.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 15:06:35 -0000

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

Robert <Robert.nr1@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Robert.nr1@gmail.com

--- Comment #2 from Robert <Robert.nr1@gmail.com> ---
Hi, 

I just run into this exact bug with:
  FreeBSD 10.0-RELEASE-p12 FreeBSD 10.0-RELEASE-p12

What is the current status on this, is the "sharenfs" property overall simply
not recommended nor used in production? (I also found this bug on the tracker:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=147881)

I have read people recommending to just use /etc/exports instead, but most
posts a quite old so I'm not sure what's recommended today.

Regards, Robert

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