From: Susan Champigny <schamp@ll.mit.edu>
To: nfs@lists.sourceforge.net
Subject: NFS problems:
Date: Fri, 16 Sep 2005 09:57:17 -0400 [thread overview]
Message-ID: <432ACF3D.6040900@ll.mit.edu> (raw)
Recieve the following infamous error when trying to mount a directory
from a SGI Origin running 6.5 on a Linux box running Redhat Enterprise
ES 4.0
mount: NFS version 3 mount failed; trying NFS version 2
Not sure what to do here, can someone give me some ideas.
2nd problem:
For some reason on the same SGI the nfs daemons appear to crap out,
breaking autofs
until I run /etc/init.d/network start; to restart the network.
Some the of errors in /var/adm/SYSLOG are:
machinename: autofsd [pid] pingnfs: nfs3 port=0 155.34.3.xx program not
registered
machinename: autofsd [pid] pingnfs: nfs2 port=0 155.34.3.xx program not
registered
I would appreciate any comments.
Thank you.
--
Susan M. Champigny
MIT Lincoln Laboratory
Space Situational Awareness Group
781-981-2918
schamp@ll.mit.edu
The information transmitted in this e-mail is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, retransmission, dissemination or other use of or taking
of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.
If you received this e-mail in error, please contact the sender and delete the email and any attached material immediately. Thank you.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2005-09-16 13:58 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=432ACF3D.6040900@ll.mit.edu \
--to=schamp@ll.mit.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.