From khera@kciLink.com  Thu Jun 21 12:06:51 2001
Return-Path: <khera@kciLink.com>
Received: from yertle.kciLink.com (yertle.kcilink.com [216.194.193.105])
	by hub.freebsd.org (Postfix) with ESMTP id 8308C37B408
	for <FreeBSD-gnats-submit@freebsd.org>; Thu, 21 Jun 2001 12:06:51 -0700 (PDT)
	(envelope-from khera@kciLink.com)
Received: from onceler.kciLink.com (onceler.kciLink.com [216.194.193.106])
	by yertle.kciLink.com (Postfix) with ESMTP id 6522A2E45F
	for <FreeBSD-gnats-submit@freebsd.org>; Thu, 21 Jun 2001 15:06:47 -0400 (EDT)
Received: (from khera@localhost)
	by onceler.kciLink.com (8.11.4/8.11.3) id f5LJ6lJ05598;
	Thu, 21 Jun 2001 15:06:47 -0400 (EDT)
	(envelope-from khera)
Message-Id: <200106211906.f5LJ6lJ05598@onceler.kciLink.com>
Date: Thu, 21 Jun 2001 15:06:47 -0400 (EDT)
From: <khera@kciLink.com>
Reply-To: khera@kciLink.com
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: NFS_NOSERVER kernel option causes zillions of syslog messages
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         28325
>Category:       bin
>Synopsis:       NFS_NOSERVER causes zillions of Device not configured messages
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jun 21 12:10:03 PDT 2001
>Closed-Date:    Thu Jun 21 17:42:07 PDT 2001
>Last-Modified:  Thu Jun 21 17:57:17 PDT 2001
>Originator:     Vivek Khera
>Release:        FreeBSD 4.3-STABLE i386
>Organization:
>Environment:
System: FreeBSD onceler.kciLink.com 4.3-STABLE FreeBSD 4.3-STABLE #6: Mon Jun 11 12:39:31 EDT 2001 khera@yertle.kciLink.com:/u/yertle2/usr.obj/amd/onceler/u/onceler1/usr/src/sys/ONCELER i386


	
>Description:

I built a kernel with NFS and NFS_NOSERVER options.  When I went to
mount the remote file system, I started getting these messages in the syslog:

Jun 20 15:34:06 m02 mount_nfs:[42953]: nfssvc err Device not configured
Jun 20 15:34:36 m02 last message repeated 678049 times
Jun 20 15:36:37 m02 last message repeated 2878406 times
Jun 20 15:42:19 m02 last message repeated 8128132 times

The file system mounted fine, and copying data back and forth was
working ok, with no noticeable speed issues.

>How-To-Repeat:
	

build a kernel with NFS and NFS_NOSERVER options enabled.

>Fix:

	
Workaround is not to specify NFS_NOSERVER
>Release-Note:
>Audit-Trail:

From: Ian Dowse <iedowse@maths.tcd.ie>
To: khera@kciLink.com
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/28325: NFS_NOSERVER kernel option causes zillions of syslog messages 
Date: Thu, 21 Jun 2001 20:58:19 +0100

 In message <200106211906.f5LJ6lJ05598@onceler.kciLink.com>, khera@kciLink.com w
 rites:
 >I built a kernel with NFS and NFS_NOSERVER options.  When I went to
 >mount the remote file system, I started getting these messages in the syslog:
 >
 >Jun 20 15:34:06 m02 mount_nfs:[42953]: nfssvc err Device not configured
 >Jun 20 15:34:36 m02 last message repeated 678049 times
 >Jun 20 15:36:37 m02 last message repeated 2878406 times
 >Jun 20 15:42:19 m02 last message repeated 8128132 times
 
 What mount options are you using? It looks as if you either asked
 for NQNFS or kerberos, neither of which are likely to work well.
 
 Ian

From: Vivek Khera <khera@kcilink.com>
To: Ian Dowse <iedowse@maths.tcd.ie>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/28325: NFS_NOSERVER kernel option causes zillions of syslog messages 
Date: Thu, 21 Jun 2001 16:05:38 -0400

 >>>>> "ID" == Ian Dowse <iedowse@maths.tcd.ie> writes:
 
 ID> In message <200106211906.f5LJ6lJ05598@onceler.kciLink.com>, khera@kciLink.com w
 ID> rites:
 >> I built a kernel with NFS and NFS_NOSERVER options.  When I went to
 >> mount the remote file system, I started getting these messages in the syslog:
 
 ID> What mount options are you using? It looks as if you either asked
 ID> for NQNFS or kerberos, neither of which are likely to work well.
 
 I use NQNFS (-q option to mount).  Why would this not be expected to
 work?  The mount_nfs man page says nothing about it.  Thanks.

From: Ian Dowse <iedowse@maths.tcd.ie>
To: Vivek Khera <khera@kcilink.com>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/28325: NFS_NOSERVER kernel option causes zillions of syslog messages 
Date: Thu, 21 Jun 2001 21:24:35 +0100

 In message <15154.21394.258675.13215@onceler.kciLink.com>, Vivek Khera writes:
 >
 >ID> What mount options are you using? It looks as if you either asked
 >ID> for NQNFS or kerberos, neither of which are likely to work well.
 >
 >I use NQNFS (-q option to mount).  Why would this not be expected to
 >work?  The mount_nfs man page says nothing about it.  Thanks.
 
 NQNFS is an experimental protocol based on NFSv2 that is not in
 wide use, and it's implementation has suffered significant bit-rot
 over the years. Unless you have a really good reason to use it and
 you understand fully what it is and what it does, I'd advise using
 the newer and much more widely used NFSv3, which is the default
 anyway.
 
 Ian

From: Peter Wemm <peter@wemm.org>
To: Ian Dowse <iedowse@maths.tcd.ie>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: bin/28325: NFS_NOSERVER kernel option causes zillions of syslog messages 
Date: Thu, 21 Jun 2001 13:53:38 -0700

 Ian Dowse wrote:
 > The following reply was made to PR bin/28325; it has been noted by GNATS.
 > 
 > From: Ian Dowse <iedowse@maths.tcd.ie>
 > To: Vivek Khera <khera@kcilink.com>
 > Cc: FreeBSD-gnats-submit@freebsd.org
 > Subject: Re: bin/28325: NFS_NOSERVER kernel option causes zillions of syslog 
     messages 
 > Date: Thu, 21 Jun 2001 21:24:35 +0100
 > 
 >  In message <15154.21394.258675.13215@onceler.kciLink.com>, Vivek Khera write
     s:
 >  >
 >  >ID> What mount options are you using? It looks as if you either asked
 >  >ID> for NQNFS or kerberos, neither of which are likely to work well.
 >  >
 >  >I use NQNFS (-q option to mount).  Why would this not be expected to
 >  >work?  The mount_nfs man page says nothing about it.  Thanks.
 >  
 >  NQNFS is an experimental protocol based on NFSv2 that is not in
 >  wide use, and it's implementation has suffered significant bit-rot
 >  over the years. Unless you have a really good reason to use it and
 >  you understand fully what it is and what it does, I'd advise using
 >  the newer and much more widely used NFSv3, which is the default
 >  anyway.
 
 The NQNFS code is a festering pile of excretement.  Among other things,
 the NQNFS client side *depends* on the NFS server code being present,
 and will leak kernel memory if mountd is not running (ie: the filesystem
 exporter).
 
 Cheers,
 -Peter
 --
 Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
 "All of this is for nothing if we don't go to the stars" - JMS/B5
 

From: Vivek Khera <khera@kcilink.com>
To: Ian Dowse <iedowse@maths.tcd.ie>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/28325: NFS_NOSERVER kernel option causes zillions of syslog messages 
Date: Thu, 21 Jun 2001 17:36:14 -0400

 >>>>> "ID" == Ian Dowse <iedowse@maths.tcd.ie> writes:
 
 >> I use NQNFS (-q option to mount).  Why would this not be expected to
 >> work?  The mount_nfs man page says nothing about it.  Thanks.
 
 ID> NQNFS is an experimental protocol based on NFSv2 that is not in
 ID> wide use, and it's implementation has suffered significant bit-rot
 ID> over the years. Unless you have a really good reason to use it and
 
 The man page says it is an extension to NFSv3
 
      -q      Use the leasing extensions to the NFS Version 3 protocol to main-
              tain cache consistency.  This protocol Version 2, referred to as
              Not Quite Nfs (NQNFS), is only supported by this updated release
              of NFS code.  (It is not backwards compatible with the release of
              NQNFS that went out on 4.4BSD-Lite.  To interoperate with a
 
 I guess I'll shut it off anyhow, I get warnings about too many leases
 some times.
 
 Thanks.
State-Changed-From-To: open->closed 
State-Changed-By: iedowse 
State-Changed-When: Thu Jun 21 17:42:07 PDT 2001 
State-Changed-Why:  

NQNFS is broken in many ways, and is unlikely to be fixed. However 
the wording describing the -q option to mount_mfs was very confusing, 
so I have updated mount_mfs(8) to clarify this and discourage the 
use of NQNFS. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=28325 
>Unformatted:
