Date: Thu, 10 Jul 2008 20:25:54 +0200 (CEST) From: Oliver Fromme <olli@fromme.com> To: kris@FreeBSD.org (Kris Kennaway) Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sbin/mount_nfs mount_nfs.c Message-ID: <200807101825.m6AIPsoO016253@haluter.fromme.com> In-Reply-To: <200807101753.m6AHrNCX059003@repoman.freebsd.org> from "Kris Kennaway" at Jul 10, 2008 05:53:10 PM
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > > kris 2008-07-10 17:53:10 UTC > > FreeBSD src repository > > Modified files: > sbin/mount_nfs mount_nfs.c > Log: > SVN rev 180435 on 2008-07-10 17:53:10Z by kris > > Fix -o mntudp after the conversion to default TCP mounts > > Submitted by: danfe > MFC after: 1 week Does that mean you will also MFC the conversion to default TCP mounts? RELENG_7 still uses UDP by default. If you MFC that, I suggest you add an entry to src/UPDATING and possibly post a headsup to the -stable list, because the change might affect people in unexpected ways. Currently I happen to work at a customer with several NetApp filers that support TCP mounts only if the -U option is used. UDP mounts work fine. TCP mounts without the -U option just hang and require a reboot. It is probably a bug in the filers' firmware, but said customer cannot update the firmware for other, unrelated reasons. Another case where people might be bitten is when there are packet filter rules that allow UDP mounts only. An appropriate UPDATING entry and/or a HEADSUP in -stable might save some people's day. Best regards Oliver -- Oliver Fromme, Bunsenstr. 13, 81735 Muenchen, Germany ``We are all but compressed light'' (Albert Einstein)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200807101825.m6AIPsoO016253>