From owner-freebsd-current@FreeBSD.ORG  Sun Jun 21 12:44:39 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 23E041065672;
	Sun, 21 Jun 2009 12:44:39 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from kennaway-macbookpro.config (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 2A00C8FC18;
	Sun, 21 Jun 2009 12:44:37 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <4A3E2B35.1050906@FreeBSD.org>
Date: Sun, 21 Jun 2009 13:44:37 +0100
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: Rick Macklem <rmacklem@uoguelph.ca>
References: <4A38C92F.7050809@FreeBSD.org>
	<Pine.GSO.4.63.0906171118170.11250@muncher.cs.uoguelph.ca>
In-Reply-To: <Pine.GSO.4.63.0906171118170.11250@muncher.cs.uoguelph.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: FreeBSD Current <freebsd-current@FreeBSD.org>,
	Pawel Jakub Dawidek <pjd@FreeBSD.org>, Kip Macy <kmacy@FreeBSD.org>
Subject: Re: destroyed NFS exported filesystems not removed from
	/etc/zfs/exports
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Jun 2009 12:44:39 -0000

Rick Macklem wrote:
> 
> 
> On Wed, 17 Jun 2009, Kris Kennaway wrote:
> 
>> mountd was failing to start after an upgrade, with lots of log entries 
>> like:
>>
>> Jun 17 10:19:22 <daemon.err> pointyhat mountd[855]: bad exports list 
>> line /a/portbuild/i386/20090421213917
>> Jun 17 10:19:22 <daemon.err> pointyhat mountd[855]: bad exports list 
>> line /a/portbuild/i386/7-exp/builds/20090422073914/src
>> Jun 17 10:19:22 <daemon.err> pointyhat mountd[855]: bad exports list 
>> line /a/portbuild/i386/8-exp/builds/20080814181849/ports
>>
>> These came from /etc/zfs/exports, and refer to filesystems that used 
>> to exist & were exported, but which have been destroyed.  These were 
>> not cleaned up at destroy time.
>>
>> zfs unshare -a didn't clean this file up either, I had to remove it 
>> and recreate.
>>
>> Also, mountd was treating these as fatal errors at runtime and failing 
>> to start.  I think this is a recent change in mountd, since this used 
>> to work even with the stale entries (the 200808 filesystem was 
>> destroyed in 2008, and mountd has started correctly after numerous 
>> reboots until the upgrade I just did from a May 9 world+kernel).
>>
> Well, the most recent change pre-May 9 done to mountd.c was on Nov. 3. It
> involved adding security flavors to the exports.
> (http://svn.freebsd.org/viewc/base/ is your friend:-)

It worked as of May 9.  What about changes made after May 9?

Kris

> 
> I can't think of how that might have broken things, but I don't know
> diddly about zfs.
> 
> rick
> 
>