From owner-freebsd-questions@FreeBSD.ORG Fri May 3 12:09: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 DE02B80C for ; Fri, 3 May 2013 12:09:27 +0000 (UTC) (envelope-from bah@bananmonarki.se) Received: from feeder.usenet4all.se (1-1-1-38a.far.sth.bostream.se [82.182.32.53]) by mx1.freebsd.org (Postfix) with ESMTP id 6B60C1C4D for ; Fri, 3 May 2013 12:09:25 +0000 (UTC) Received: from kw.news4all.se (localhost [127.0.0.1]) by feeder.usenet4all.se (8.13.1/8.13.1) with ESMTP id r43C9Gb3008698; Fri, 3 May 2013 14:09:17 +0200 (CEST) (envelope-from bah@bananmonarki.se) Message-ID: <5183A8BA.7040309@bananmonarki.se> Date: Fri, 03 May 2013 14:08:26 +0200 From: Bernt Hansson User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130321 Thunderbird/17.0.4 MIME-Version: 1.0 To: Daniel Feenberg Subject: Re: Restarting exports disturbs clients References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-questions@freebsd.org" 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 12:09:27 -0000 2013-05-03 12:49, Daniel Feenberg skrev: > > When we change the exportfs file on our FreeBSD 9.1 fileserver: > > kill -HUP `cat /var/run/mountd.pid` That seems a bit harsh, try /etc/rc.d/nfsd restart or /etc/nfsserver restart. > 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