Date: Mon, 7 Nov 2016 21:40:44 +0000 From: Colin Percival <cperciva@tarsnap.com> To: Rick Macklem <rmacklem@uoguelph.ca>, "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: Mount protocol/showmount vs NFSv4 Message-ID: <0100015840bc7db4-7afb588d-fe3d-4623-b41f-ceabb6e5a426-000000@email.amazonses.com> In-Reply-To: <YTXPR01MB01893AD86D5F1280DC63CA4BDDA40@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> References: <YTXPR01MB01893AD86D5F1280DC63CA4BDDA40@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for bringing this to the list, Rick. (This started with me asking Rick why unmounting my nfsv4 mount was sending UDP packets.) On 11/06/16 12:51, Rick Macklem wrote: > NFSv4 doesn't use the Mount protocol at all and does everything via the NFSv4 protocol > serviced at port #2049. It doesn't use the Mount protocol while the filesystem is in use, but our umount(8) code does send UDP packets (which I understand are for the Mount protocol) when unmounting an nfsv4 mount. > I have never done anything about this, since most were still using NFSv3, but it seems > that maybe something should be done now? > - What do people think of having a new option on mountd(8) that would be used for > NFSv4 only servers that disables servicing of Mount RPCs. Done in isolation, it seems that this would guarantee that unmounting an nfsv4 filesystem will result in umount(8) hanging while it waits for responses to the UDP packets it sends. So I'd think that we should fix the client side to stop sending those first? -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0100015840bc7db4-7afb588d-fe3d-4623-b41f-ceabb6e5a426-000000>