From owner-freebsd-current Sat Apr 19 06:58:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA17405 for current-outgoing; Sat, 19 Apr 1997 06:58:31 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA17399 for ; Sat, 19 Apr 1997 06:58:24 -0700 (PDT) Received: from Jupiter.Mcs.Net (karl@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id IAA02823; Sat, 19 Apr 1997 08:58:22 -0500 (CDT) Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.5/8.8.2) id IAA08422; Sat, 19 Apr 1997 08:58:22 -0500 (CDT) Message-ID: <19970419085821.10580@Jupiter.Mcs.Net> Date: Sat, 19 Apr 1997 08:58:21 -0500 From: Karl Denninger To: Doug Rabson Cc: Karl Denninger , current@freebsd.org Subject: Re: Danger Will Robinson References: <19970418124839.37391@Jupiter.Mcs.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 In-Reply-To: ; from Doug Rabson on Sat, Apr 19, 1997 at 09:22:17AM +0100 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, Apr 19, 1997 at 09:22:17AM +0100, Doug Rabson wrote: > On Fri, 18 Apr 1997, Karl Denninger wrote: > > > On Fri, Apr 18, 1997 at 05:27:35PM +0100, Doug Rabson wrote: > > > I have changed both mount_nfs and amd to use NFSv3 in preference to v2 if > > > it is supported by the server. This means that machines which have been > > > using v2 by default will now start using the v3 protocol. I believe that > > > the v3 support in current is stable enough to make it the default but no > > > doubt someone will prove me wrong. > > > > > > To revert to the old behaviour, add the nfsv2 option to either /etc/fstab > > > for static mounts or to the amd map defaults for automounts. This will > > > force the use of the older protocol. > > > > > > -- > > > Doug Rabson Mail: dfr@nlsystems.com > > > Nonlinear Systems Ltd. Phone: +44 181 951 1891 > > > > > > > Are you saying that if I'm running a -CURRENT client I can mount a > > filesystem over NFS and the system will NOT blow up if I execute something > > over that NFS mounted link -- and its V3? > > > > This is definitely not true by default with -CURRENT kernels, and I'd like > > to know if it is with these changes in place. > > I can't yet reproduce your problem, so no. Could you give me a few more > details? What blows up? Does the process fault or the kernel? If the > kernel, where? Packet traces etc. would also be useful. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 951 1891 It is not NFS specific. Try running a web server on -CURRENT using httpd 1.5.2. The kernel will blow chunks within minutes with a "page not present" fault. This is true whether the executable is on a LOCAL disk or over NFS. The -CURRENT kernel is NOT stable in this sort of environment. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | 99 Analog numbers, 77 ISDN, http://www.mcs.net/ Voice: [+1 312 803-MCS1 x219]| NOW Serving 56kbps DIGITAL on our analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal