linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Anderson <ezjab-EkmVulN54Sk@public.gmane.org>
To: Jim Rees <rees@umich.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: (k)ubuntu NFS bug
Date: Sat, 30 Apr 2011 16:19:30 -0400	[thread overview]
Message-ID: <4DBC6ED2.9050702@ieee.org> (raw)
In-Reply-To: <20110430192038.GA2081-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>


Thanks again for the suggestions. I'm not sure what solution would work, 
if anything, but my problem is fixed.

I upgraded all of my systems to Kubuntu 10.10 and NFS is working again.
I assume there is some type of compatibility bug, but it is not work
tracing the root problem now. This took a bit of time, but it is 
probably for the better that the other systems are all upgraded now.

Jim Anderson
ezjab-EkmVulN54Sk@public.gmane.org
(908)329-0586

On 04/30/2011 03:20 PM, Jim Rees wrote:
> Jim Anderson wrote:
>
>    Thank you for the suggestions. If I understood right, I should try:
>
>    >>>  mount -t nfs duke:/mnt/myFiles /mnt/myFiles -O proto=udp
>    and
>    >>>  mount -t nfs duke:/mnt/myFiles /mnt/myFiles -O nfsvers=3
>
> I'm not sure what that will do but I don't think it's what you want.  Try
> these:
>
> mount -o proto=udp duke:/mnt/myFiles /mnt/myFiles
> mount -o nfsvers=3 duke:/mnt/myFiles /mnt/myFiles
>

      parent reply	other threads:[~2011-04-30 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 13:34 (k)ubuntu NFS buy Jim Anderson
     [not found] ` <4DBABE48.1050901-EkmVulN54Sk@public.gmane.org>
2011-04-29 15:02   ` Jim Rees
     [not found]     ` <20110429150214.GA10040-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
2011-04-30 18:53       ` (k)ubuntu NFS bug Jim Anderson
     [not found]         ` <4DBC5AA0.5090407-EkmVulN54Sk@public.gmane.org>
2011-04-30 19:20           ` Jim Rees
     [not found]             ` <20110430192038.GA2081-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
2011-04-30 20:19               ` Jim Anderson [this message]

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=4DBC6ED2.9050702@ieee.org \
    --to=ezjab-ekmvuln54sk@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rees@umich.edu \
    /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).