Restarting exports disturbs clients
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Restarting exports disturbs clients
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Restarting exports disturbs clients
On Fri, May 03, 2013 at 02:08:26PM +0200, Bernt Hansson wrote: 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. Sending SIGHUP to mountd has always been the right way to have it reread the exports file - should really be much less disruptive than restarting the service. Graham -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Restarting exports disturbs clients
On Fri, 3 May 2013, Graham Allan wrote: On Fri, May 03, 2013 at 02:08:26PM +0200, Bernt Hansson wrote: 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. Sending SIGHUP to mountd has always been the right way to have it reread the exports file - should really be much less disruptive than restarting the service. We have tried both and both disruptive NFS clients. dan feenberg Graham -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Restarting exports disturbs clients
Actually, changes to /etc/exports under FreeBSD take effect when you either kill -HUP mountd.pid or /etc/rc.d/mountd reload|restart on the nfs server, but both disrupt existing mounted shares on the nfs client. What we are looking for is an equivalent of exportfs -r under Linux. Is that available under FreeBSD? Thanks. -- mohan -- On Fri, 3 May 2013, Daniel Feenberg wrote: On Fri, 3 May 2013, Graham Allan wrote: On Fri, May 03, 2013 at 02:08:26PM +0200, Bernt Hansson wrote: 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. Sending SIGHUP to mountd has always been the right way to have it reread the exports file - should really be much less disruptive than restarting the service. We have tried both and both disruptive NFS clients. dan feenberg Graham -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
