9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio de Re lucio@proxima.alt.za
Subject: [9fans] nfsserver
Date: Tue, 21 Apr 1998 12:59:21 +0200	[thread overview]
Message-ID: <19980421105921.5J3TTG2bI8-WF3l6xdS1OqPL609xBqzooMCifnpwA60@z> (raw)

According to arisawa@plan9.aichi-u.ac.jp :
> 
> ar> /etc/mount -o soft,intr plan9:9fs /n/9fs
> mount: plan9:9fs on /n/9fs: Stale NFS file handle
> mount: giving up on:
>    /n/9fs
> 
OK, time to ask the experts for some additional information.

1. The Stale NFS file handle is produced by nfsserver, based on a 
missing machine name in the client credentials.  Is this a Unix bug?
Three different releases of NetBSD produce the same result, user 0 and 
user 301 both producing 0@ and 301@ as the credentials.  The result is 
an empty client ID which cannot be matched in the configuration file
(should it be matched?).

2. NetBSD 1.2.1 and 1.3 both assume NFS version 3 and do not try a 
version 2 possibility.  Does the portmapper have the ability to trigger 
the demotion, or do I need to report to the NetBSD group that they 
should activate such demotion in their mount_nfs code?  Requesting 
version 2 services produces the desired result, give or take the Stale 
NFS file handle problem.

Forsyth?
-- 
Lucio de Re (lucio@proxima.alt.za)
Disclaimer: I'm working at getting my opinions to agree with me.






             reply	other threads:[~1998-04-21 10:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-21 10:59 Lucio [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-09-07 16:08 Russ
1998-09-04  7:56 forsyth
1998-09-04  6:39 forsyth
1998-09-04  0:18 Russ
1998-07-27  7:28 Kenji
1998-07-25 22:23 Russ
1998-07-25  0:30 Kenji
1998-04-23  4:31 Kenji
1998-04-23  4:31 Russ
1998-04-22  7:13 Kenji
1998-04-21 13:53 forsyth
1998-04-15 23:27 arisawa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19980421105921.5J3TTG2bI8-WF3l6xdS1OqPL609xBqzooMCifnpwA60@z \
    --to=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).