mount -t nfs4 fails w/ permission denied; how to debug? (FC3)
dan
info at hostinthebox.net
Wed Mar 16 18:06:44 UTC 2005
Rick Stevens wrote:
> Ankush Grover wrote:
>
>> On Tue, 15 Mar 2005 22:23:48 +0000, Will Partain
>> <will.partain at verilab.com> wrote:
>>
>>> In a test setup with FC3 client and server, I can successfully
>>>
>>> sudo mount -t nfs albus:/._disc1/sysadm/test1 /mnt/test1
>>>
>>> (getting an nfs v3 mount). If I instead...
>>>
>>> sudo mount -t nfs4 albus:/._disc1/sysadm/test1 /mnt/test1
>>>
>>> ... I get "mount: permission denied". Nothing appears in the logs of
>>> either machine (well, one uninteresting SELinux message; SELinux is
>>> not enforced on either machine). I believe that bits are getting to
>>> the server: certainly running ethereal against port 2049 on the server
>>> shows chit-chat at the expected time. This is without Kerberos,
>>> i.e. it should be doing sec=unix.
>>>
>>> So the question: how can I get something to tell me more about what's
>>> going on? Thanks,
>>>
>>
>> hey,
>>
>> why ru giving nfs4 where in the above line you have given nfs ,try
>> to give nfs only not nfs4.
>> for nfs to work ,port 111(portmapper),mountd,port 2049(nfs),rpc should
>> be running on the server.
>
>
> There is no "nfs4" filesystem type. If you want to use NFSV4, then
> add "nfsvers=4" in the mount options field:
>
> sudo mount -t nfs -o nfsvers=4 albus:/._disc1/sysadm/test1 /mnt/test1
>
> You should also note that many NFSV4 hosts no longer support UDP (the
> default NFS network protocol) and only work with TCP. You may need to
> set the options to:
>
> -o nfsvers=4,proto=tcp
>
> for it to work under NFSV4.
<snip blah blah blah>
There is an nfs4 filesystem type. man mount.
Will, nfs messages often appear in /var/log/messages, which should give
you some help. You can also manually launch the NFS server in the
foreground to see errors that happen in real-time.
Hope that helps
-dant
More information about the fedora-list
mailing list