Date: Mon, 8 May 2017 00:50:53 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Claude Buisson <clbuisson@orange.fr>, FreeBSD Current <freebsd-current@freebsd.org> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Recent FreeBSD, NFSv4 and /var/db/mounttab Message-ID: <YTXPR01MB01897BBE282D188EAE86F740DDEE0@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <17039eeb-fd0d-a0f7-19bf-48c75013f222@orange.fr> References: <20c2baca-ba91-19b4-db95-5352b56019c1@orange.fr> <YTXPR01MB018915F50E09FC0DD8CF0214DD4D0@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> <YTXPR01MB018914B30689B00D1D9E7DBADDE90@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>, <17039eeb-fd0d-a0f7-19bf-48c75013f222@orange.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
Claude Buisson wrote: >On 05/07/2017 21:09, Rick Macklem wrote: >> Claude Buisson wrote: >>> Hi, >>> >>> Last month, I started switching all my systems (stable/9, stable/10, >>> stable/11 and current) to NFSv4, and I found that: >>> >>> on current (svn 312652) an entry is added to /var/db/mounttab by >>> mount_nfs(8), but not suppressed by umount(8). It can be suppressed by >>> rpc.umntall(8). >>> >>> The same anomaly appears on stable/11 after upgrading to svn 312950. >>> >>> It is relatively easy to trace this anomaly to r308871 on current and >>> its MFHs (r309517 for stable/11). >>> >>> Patching sbin/umount/umount.c to restore the RPC call for NFSv4 makes >>> umount(8) suppress the mounttab entry as before. >>> >>> I do not know what is the proper solution, as suppressing the >>> modification of mounttab by mount_nfs(8) for NFSv4 could be an (more >>> complicated) alternative ! I chose this alternative, since NFSv4 has nothing to do with the Mount prot= ocol. A one line patch to do this is now committed to head as r317931. Thanks for reporting this, rick [stuff snipped]=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTXPR01MB01897BBE282D188EAE86F740DDEE0>