From owner-freebsd-questions@FreeBSD.ORG Fri May 3 11:22:27 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 13A98AEC for ; Fri, 3 May 2013 11:22:27 +0000 (UTC) (envelope-from feenberg@nber.org) Received: from mail2.nber.org (mail2.nber.org [66.251.72.79]) by mx1.freebsd.org (Postfix) with ESMTP id CF0B417F2 for ; Fri, 3 May 2013 11:22:26 +0000 (UTC) Received: from nber6 (nber6.nber.org [66.251.72.76]) by mail2.nber.org (8.14.4/8.14.4) with ESMTP id r43B3RJK046565; Fri, 3 May 2013 07:03:28 -0400 (EDT) (envelope-from feenberg@nber.org) Date: Fri, 3 May 2013 06:49:07 -0400 (EDT) From: Daniel Feenberg X-X-Sender: feenberg@nber6 To: "freebsd-questions@freebsd.org" Subject: Restarting exports disturbs clients Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.39/RELEASE, bases: 20130503 #9872595, check: 20130503 clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 May 2013 11:22:27 -0000 When we change the exportfs file on our FreeBSD 9.1 fileserver: kill -HUP `cat /var/run/mountd.pid` it kills the jobs on clients that have files open on the fileserver. This is pretty inconvenient for users (and us). Is there a way around this? We have noticed that a Linux fileserver can restart nfs without distrubing clients (other than a short pause). The Linux restart doesn't restart the locking mechanism - is that the difference? We could do without locks, even without NFSv4, for that matter, if it would let us change exports without disturbing users. Perhaps there there is an NFS shutdown procedure that we should be using? Daniel Feenberg NBER