mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: taroon-list@vger.kernel.org, redhat-list@redhat.com
Subject: Kernel 2.4.21 or RHEL AS3 Bug under Taroon?
Date: Tue, 7 Feb 2006 06:43:36 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0602070608470.23943@p34> (raw)

I have a quad-cpu server running RHEL AS 3, Taroon that acts as an NFS 
server for some other machines.

It had a 390 uptime when the problem occured.

Essentially, the directory paths it serves out stopped working, attempting 
to mount the directory on two client boxes results in:

box1# mount rhelas3_box:/share1 /mnt/share1
mount: RPC: Program not registered

box2# mount rhelas3_box:/share2 /mnt/share2
mount: RPC: Program not registered

My guess as to what happened is portmap died on the server and then the 
rpc commands could not be established between the server and the clients.

The options used for the mount are as follows:
rhelas3_box:/share1  /mnt/share1  nfs 
ro,tcp,nfsvers=3,rsize=8192,timeo=11,hard,intr,defaults
rhelas3_box:/share2  /mnt/share2  nfs 
ro,tcp,nfsvers=3,rsize=8192,timeo=11,hard,intr,defaults

On the server in /etc/exports, the shares are below:
/mnt/share1  1.2.3.4(rw,no_root_squash,sync)
/mnt/share2  1.2.3.4(rw,no_root_squash,sync)

Is this more of a kernel issue or specifically the portmap daemon?  I have 
not seen this error in the past where NFS mounts randomly die, disappear 
or fail to work.

Other than checking the logs during the time of the failure, what is the 
best way to begin troubleshooting this issue?

Thanks,

Justin.



                 reply	other threads:[~2006-02-07 11:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.64.0602070608470.23943@p34 \
    --to=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=redhat-list@redhat.com \
    --cc=taroon-list@vger.kernel.org \
    /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®