Date: Sun, 23 Jan 2005 04:06:55 GMT From: Matthias Buelow <mkb@incubus.de> To: freebsd-gnats-submit@FreeBSD.org Subject: bin/76590: adding -mapall in nfs exports requires reboot Message-ID: <200501230406.j0N46tje051010@www.freebsd.org> Resent-Message-ID: <200501230410.j0N4AJf9038904@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 76590
>Category: bin
>Synopsis: adding -mapall in nfs exports requires reboot
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Jan 23 04:10:19 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: Matthias Buelow
>Release: 5.3-STABLE
>Organization:
>Environment:
FreeBSD xxx 5.3-STABLE FreeBSD 5.3-STABLE #6: Fri Jan 21 10:47:22 CET 2005 xxx:/usr/obj/usr/src/sys/xxx i386
>Description:
Adding a -mapall option to an entry in /etc/exports doesn't seem to have any effect, even when restarting the nfs server and mountds. Only after rebooting the server the change comes into effect. It is nonsensical that a change of nfsd export attributes requires a system reboot, instead of just an nfs server restart.
>How-To-Repeat:
I have the following line in /etc/exports:
/usr -mapall=mkb:mkb -network 192.168.0.0 -mask 255.255.255.0
Before that, I already exported it without the mapall directive.
Mounting on clients worked in both cases but after adding the mapall directive, no remapping was done. I also tried with numerical ids, without groups, and various permutations thereof.
I restarted nfsd with /etc/rc.d/nfsd restart, /etc/rc.d/mountd restart, and even stopped and started the servers manually.
The filesystem was unmounted on the client during restarts.
I noticed that nfsiod wasn't affected by these restarts.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501230406.j0N46tje051010>