Bug 28325

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

>>>>> "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.

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

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

>>>>> "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.

Comment 6 iedowse 2001-06-22 01:42:07 UTC

State Changed
From-To: open->closed


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.