nfs mount fails in Ubuntu 10, but not with -v

[Stuart Reynolds]

  remotehost:/remotedir localmountpoint nfs owner,rw,proto=udp   0 0

was the answer.
Thanks!
- Stu

On Wed, Jun 9, 2010 at 9:26 PM, Tom H <tomh0665 at gmail.com> wrote:
> On Wed, Jun 9, 2010 at 9:47 PM, Stuart Reynolds
> <ubuntu-users at stuartreynolds.net> wrote:
>> I've tried:
>>
>>      (1)  mount    -t nfs remotehost:/remotedir localmountpoint -o owner,rw
>>      (2)  mount -v -t nfs remotehost:/remotedir localmountpoint -o owner,rw
>>
>> (1) Used to work with Ubuntu 9 and now fails with Ubuntu 10
>> (2.6.32-21-generic kernel) with the error:
>>
>>       mount.nfs: an incorrect mount option was specified
>>
>> Strangely, adding -v (verbose) in (2) makes the problem go away.
>>
>> This is currently a blocker for me because the fstab line:
>>
>>       remotehost:/remotedir localmountpoint nfs owner,rw   0 0
>>
>> causes the same error (I don't believe I can specify verbose in fstab).
>>
>> Is this a bug in mount or are my options really incorrect?
>
> IIRC, this has come up before (either on this list or another) and the
> solution was to specify a udp mount because the default is tcp. (The
> success with "-v" was unexplained.)
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>