From nobody@FreeBSD.org  Mon Aug 23 19:58:21 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6A74E16A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 23 Aug 2004 19:58:21 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4A14D43D45
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 23 Aug 2004 19:58:21 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i7NJwKF4039197
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 23 Aug 2004 19:58:20 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i7NJwKMj039196;
	Mon, 23 Aug 2004 19:58:20 GMT
	(envelope-from nobody)
Message-Id: <200408231958.i7NJwKMj039196@www.freebsd.org>
Date: Mon, 23 Aug 2004 19:58:20 GMT
From: Joe <fbsd_user@a1poweruser.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: 5.3 beta1 nfs problem
X-Send-Pr-Version: www-2.3

>Number:         70880
>Category:       kern
>Synopsis:       [nfs] 5.3 beta1 nfs problem
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    rwatson
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Aug 23 20:00:38 GMT 2004
>Closed-Date:    Thu Jun 08 23:00:09 GMT 2006
>Last-Modified:  Thu Jun 08 23:00:09 GMT 2006
>Originator:     Joe
>Release:        5.3 beta1 8/20 build
>Organization:
home
>Environment:
>Description:
Downloaded 5.3 beta1-i386-mininstall.iso, ran md5 checksum and count
matched, burned to cd and installed using standard/kern-dev. Answered
no to both nfs option questions. On first boot nfs server is started.
ps ax command shows nfsiod1, nfsiod2, and nfsiod3 tasks running.
/etc/rc.conf does not have any nfs override statements. Only way to
get rid of nfs is to comment out nfs statements in kernel source and
recompile kernel. This is an error that needs fixing.     
>How-To-Repeat:
      
>Fix:
      
>Release-Note:
>Audit-Trail:

From: Ceri Davies <ceri@submonkey.net>
To: Joe <fbsd_user@a1poweruser.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/70880: 5.3 beta1 nfs problem
Date: Mon, 23 Aug 2004 23:03:24 +0100

 On Mon, Aug 23, 2004 at 07:58:20PM +0000, Joe wrote:
 
 > Downloaded 5.3 beta1-i386-mininstall.iso, ran md5 checksum and count
 > matched, burned to cd and installed using standard/kern-dev. Answered no
 > to both nfs option questions. On first boot nfs server is started. ps ax
 > command shows nfsiod1, nfsiod2, and nfsiod3 tasks running. /etc/rc.conf
 > does not have any nsf override statements. Only way to get rid of nfs is
 > to comment out nfs statements in kernel source and recompile kernel.
 > This is an error that needs fixing.
 
 nfsiod is a NFS client-side process.  In this instance they are kernel
 threads and you can turn them off if you like by adding
 vfs.nfs.iodmin=0 to /etc/sysctl.conf, or by removing the NFSCLIENT
 option from your kernel configuration.
 
 I have changed the Severity of this PR to something more realistic.
 
 Ceri
 -- 
 It is not tinfoil, it is my new skin.  I am a robot.

From: "fbsd_user" <fbsd_user@a1poweruser.com>
To: "Ceri Davies" <ceri@submonkey.net>
Cc: <freebsd-gnats-submit@FreeBSD.org>
Subject: RE: kern/70880: 5.3 beta1 nfs problem
Date: Mon, 23 Aug 2004 19:54:31 -0400

 Ceri wrote:
 > On Mon, Aug 23, 2004 at 07:58:20PM +0000, Joe wrote:
 >
 >> Downloaded 5.3 beta1-i386-mininstall.iso, ran md5 checksum and
 count
 >> matched, burned to cd and installed using standard/kern-dev.
 >> Answered no to both nfs option questions. On first boot nfs
 server
 >> is started. ps ax command shows nfsiod1, nfsiod2, and nfsiod3
 tasks
 >> running. /etc/rc.conf does not have any nsf override statements.
 >> Only way to get rid of nfs is to comment out nfs statements in
 >> kernel source and recompile kernel. This is an error that needs
 >> fixing.
 >
 > nfsiod is a NFS client-side process.  In this instance they are
 kernel
 > threads and you can turn them off if you like by adding
 > vfs.nfs.iodmin=0 to /etc/sysctl.conf, or by removing the NFSCLIENT
 > option from your kernel configuration.
 >
 > I have changed the Severity of this PR to something more
 realistic.
 >
 > Ceri
 
 Ceri
 Thanks for the work around info, But that's not the point of this
 bug report. In case you missed the meaning: there should not be any
 nfs anything running on a clean install when the sysinstall
 questions to enable nfs are answered as no. This is not something
 that has ever been part of past stable releases so it must be turned
 on in the kernel by mistake. The release built team must build a
 true kernel.generic module which has kernel debugging and nfs kernel
 options turned off. Creating a stable 5.3 release is my
 understanding of the goal of the 5.3 beta weekly build series.
 Reports of these kinds of bugs get a high severity so they get fixed
 by next weeks build so why would you change this PR's Severity? If
 anything you should have directed this PR to the leader of the
 release build team so they can address this bug by next Fridays
 build.
 
 Joe
 
 
 
 
 
 

From: Giorgos Keramidas <keramida@freebsd.org>
To: fbsd_user <fbsd_user@a1poweruser.com>
Cc: bug-followup@freebsd.org
Subject: Re: kern/70880: 5.3 beta1 nfs problem
Date: Tue, 24 Aug 2004 17:51:28 +0300

 On 2004-08-24 00:00, fbsd_user <fbsd_user@a1poweruser.com> wrote:
 >  Thanks for the work around info, But that's not the point of this
 >  bug report. In case you missed the meaning: there should not be any
 >  nfs anything running on a clean install when the sysinstall
 >  questions to enable nfs are answered as no. This is not something
 >  that has ever been part of past stable releases so it must be turned
 >  on in the kernel by mistake. The release built team must build a
 >  true kernel.generic module which has kernel debugging and nfs kernel
 >  options turned off. Creating a stable 5.3 release is my
 >  understanding of the goal of the 5.3 beta weekly build series.
 >  Reports of these kinds of bugs get a high severity so they get fixed
 >  by next weeks build so why would you change this PR's Severity? If
 >  anything you should have directed this PR to the leader of the
 >  release build team so they can address this bug by next Fridays
 >  build.
 
 There's always a balance that the release engineering team has to strike
 between features that some users might want to have in the default
 installation and the features that some people might want to keep turned
 off.  Having NFSCLIENT in the GENERIC kernels minimizes the steps one has
 to go through in order to use a recently installed machine as an NFS
 client.  I'd like to see this stay in the installation kernel as long as
 possible.
 
 Would a workaround like this be ok for you Joe?
 
 	- If the user explicitly disables NFS during installation add this
 to the installed /etc/sysctl.conf:
 
 	vfs.nfs.iodmin=0
 

From: "JJB" <Barbish3@adelphia.net>
To: "Giorgos Keramidas" <keramida@freebsd.org>,
	"fbsd_user" <fbsd_user@a1poweruser.com>
Cc: <bug-followup@freebsd.org>
Subject: RE: kern/70880: 5.3 beta1 nfs problem
Date: Tue, 24 Aug 2004 11:29:46 -0400

 Giorgos Keramidas wrote:
 > On 2004-08-24 00:00, fbsd_user <fbsd_user@a1poweruser.com> wrote:
 >>  Thanks for the work around info, But that's not the point of
 this
 >>  bug report. In case you missed the meaning: there should not be
 any
 >>  nfs anything running on a clean install when the sysinstall
 >>  questions to enable nfs are answered as no. This is not
 something
 >>  that has ever been part of past stable releases so it must be
 turned
 >>  on in the kernel by mistake. The release built team must build a
 >>  true kernel.generic module which has kernel debugging and nfs
 kernel
 >>  options turned off. Creating a stable 5.3 release is my
 >>  understanding of the goal of the 5.3 beta weekly build series.
 >>  Reports of these kinds of bugs get a high severity so they get
 fixed
 >>  by next weeks build so why would you change this PR's Severity?
 If
 >>  anything you should have directed this PR to the leader of the
 >>  release build team so they can address this bug by next Fridays
 >>  build.
 >
 > There's always a balance that the release engineering team has to
 > strike between features that some users might want to have in the
 > default installation and the features that some people might want
 to
 > keep turned off.  Having NFSCLIENT in the GENERIC kernels
 minimizes
 > the steps one has to go through in order to use a recently
 installed
 > machine as an NFS client.  I'd like to see this stay in the
 > installation kernel as long as possible.
 >
 > Would a workaround like this be ok for you Joe?
 >
 > 	- If the user explicitly disables NFS during installation add
 this
 > to the installed /etc/sysctl.conf:
 >
 > 	vfs.nfs.iodmin=0
 
 That works for me, but lets not be short sighted. NFS has 2
 versions: the client and the server. One or the other version can be
 selected during the sysinstall process. Provisions must be made to
 enable server version from sysinstall. Is there a sysctl.conf knob
 to toggle nfs server on and off like there is for nfsclient?
 
 How about having  /etc/sysctl.conf default to disabling both nfs
 client and server, and when sysinstall nfs enable question is
 answered as yes then remove the correct entry from /etc/sysctl.conf
 as part of the sysinstall process. This sounds like the correct
 solution to me.
 
 
 
 
 
 
 
 

From: Giorgos Keramidas <keramida@freebsd.org>
To: JJB <Barbish3@adelphia.net>,
	fbsd_user <fbsd_user@a1poweruser.com>
Cc: bug-followup@freebsd.org
Subject: Re: kern/70880: 5.3 beta1 nfs problem
Date: Tue, 24 Aug 2004 19:15:51 +0300

 On 2004-08-24 11:29, JJB <Barbish3@adelphia.net> wrote:
 >Giorgos Keramidas wrote:
 >> There's always a balance that the release engineering team has to
 >> strike between features that some users might want to have in the
 >> default installation and the features that some people might want to
 >> keep turned off.
 >
 > NFS has 2 versions: the client and the server. One or the other
 > version can be selected during the sysinstall process. Provisions must
 > be made to enable server version from sysinstall. Is there a
 > sysctl.conf knob to toggle nfs server on and off like there is for
 > nfsclient?
 
 Yes, of course.  It event takes care of /etc/exports and shows a sample
 exports file to the user.
 
 The initial submission of this report referred to the nfsiod daemons.
 They can be disabled as I described above, but the following also sounds
 like a good idea:
 
 > How about having /etc/sysctl.conf default to disabling both nfs client
 > and server, and when sysinstall nfs enable question is answered as yes
 > then remove the correct entry from /etc/sysctl.conf as part of the
 > sysinstall process. This sounds like the correct solution to me.

From: "JJB" <Barbish3@adelphia.net>
To: "Giorgos Keramidas" <keramida@freebsd.org>,
	"fbsd_user" <fbsd_user@a1poweruser.com>
Cc: <bug-followup@freebsd.org>
Subject: RE: kern/70880: 5.3 beta1 nfs problem
Date: Tue, 24 Aug 2004 12:28:15 -0400

 Giorgos Keramidas wrote:
 > On 2004-08-24 11:29, JJB <Barbish3@adelphia.net> wrote:
 >> Giorgos Keramidas wrote:
 >>> There's always a balance that the release engineering team has
 to
 >>> strike between features that some users might want to have in
 the
 >>> default installation and the features that some people might
 want to
 >>> keep turned off.
 >>
 >> NFS has 2 versions: the client and the server. One or the other
 >> version can be selected during the sysinstall process. Provisions
 >> must be made to enable server version from sysinstall. Is there a
 >> sysctl.conf knob to toggle nfs server on and off like there is
 for
 >> nfsclient?
 >
 > Yes, of course.  It event takes care of /etc/exports and shows a
 > sample exports file to the user.
 >
 > The initial submission of this report referred to the nfsiod
 daemons.
 > They can be disabled as I described above, but the following also
 > sounds like a good idea:
 >
 >> How about having /etc/sysctl.conf default to disabling both nfs
 >> client and server, and when sysinstall nfs enable question is
 >> answered as yes then remove the correct entry from
 /etc/sysctl.conf
 >> as part of the sysinstall process. This sounds like the correct
 >> solution to me.
 
 This is all good to me. Can you make it happen by beta2 release
 cycle?  If not please keep me informed when it gets into the Beta
 testing cycle so I can test it before the final stable release.
 
 Thanks
 Joe
 
 
Responsible-Changed-From-To: freebsd-bugs->peter 
Responsible-Changed-By: rwatson 
Responsible-Changed-When: Mon Jan 3 23:47:31 GMT 2005 
Responsible-Changed-Why:  
Chown PR to Peter, since he put together our current nfsiod infrastructure. 
Given that we launch new nfsiod threads on demand when they are needed, is 
there any reason not to default to 0 as the minimum, and bump that up when 
the first NFS mount appears? 


http://www.freebsd.org/cgi/query-pr.cgi?pr=70880 
Responsible-Changed-From-To: peter->freebsd-bugs 
Responsible-Changed-By: peter 
Responsible-Changed-When: Tue Dec 13 04:09:27 UTC 2005 
Responsible-Changed-Why:  
Robert's suggestion is quite reasonable. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=70880 
Responsible-Changed-From-To: freebsd-bugs->rwatson 
Responsible-Changed-By: rwatson 
Responsible-Changed-When: Wed May 24 21:01:48 UTC 2006 
Responsible-Changed-Why:  
Grab ownership of this PR, cel@ pointed out that it appears stuck in 
limbo. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=70880 
State-Changed-From-To: open->patched 
State-Changed-By: rwatson 
State-Changed-When: Wed May 24 21:05:43 UTC 2006 
State-Changed-Why:  
Change PR state to patched; I've committed the change to default to 0 
nfsiod threads as nfs_nfsiod.c:1.88.  Thanks to cel@ for pointing 
out this PR got wedged.  Assuming no complains or problems, I will 
MFC this change in two weeks. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=70880 
State-Changed-From-To: patched->closed 
State-Changed-By: rwatson 
State-Changed-When: Thu Jun 8 22:59:32 UTC 2006 
State-Changed-Why:  
Merged to RELENG_6 as nfs_nfsiod.c:1.86, will appear in FreeBSD 6.2 and 
FreeBSD 7.0. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=70880 
>Unformatted:
