mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Daniel.Deimert@intermec.com>
To: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Cc: alan@redhat.com
Subject: PROBLEM: 2.2.18pre17 nfs - mount/showmount failed
Date: Mon, 13 Nov 2000 05:58:37 -0800	[thread overview]
Message-ID: <E36790918FA6D411856500508BD3B2CA1B21@eusegotmail1b.eu.intermec.com> (raw)

LINUX KERNEL PROBLEM REPORT

[1.] 2.2.18pre17 knfsd stops replying to mount or showmount requests

[2.] Full description of the problem:

After 9 days of uptime, Linux 2.2 clients could no longer mount nfs shares
from a 2.2.18pre17 server.
The client mount request was logged as authenticated by syslog, but the
client was denied access.
Running "showmount" on the server responded with a RPC error. No "dump"
request was logged to
syslog.  "rpcinfo -p localhost" showed mountd to be registered.
Restarting nfs with "service nfs restart" gave an error message when
shutting down mountd, but the restart restored things to normal.

[3.] Keywords: nfs, mountd, showmount

[4.] Kernel version: 2.2.18pre17

[5.] Output of Oops... message 
	N/A

[6.] Example program to trigger problem
	N/A

[7] Environment:

Red Hat 6.2
server running 2.2.18pre17 and nfs-utils 0.2
clients running RH 2.2.16

[X.]  Other notes:


--- 
Daniel Deimert (daniel.deimert@intermec.com)
Intermec Printers AB, Göteborg, Sweden



 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-11-13 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-13 13:58 Daniel.Deimert [this message]
2000-11-13 17:09 ` [NFS] " H . J . Lu

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=E36790918FA6D411856500508BD3B2CA1B21@eusegotmail1b.eu.intermec.com \
    --to=daniel.deimert@intermec.com \
    --cc=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.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

all inboxes | Powered by JetHome®