I have been trying to setup an NFS v4 File Server but have come across
an odd issue.* Mounting the /nfs4exports/share appears to be successful
and the information displayed about partition size and free space seem
correct but if I try to do anything inside the mounted directory the
client will just hang.* Does anyone have any idea what I am missing??*
I have try disabling all firewalls and selinux* but it doesn't seem to
make any difference
I have taken a look at http://www.brennan.id.au/19-Network_File_System.html#nfs4
and http://blog.laimbock.com/2009/05/21/nfsv4-on-centos-53-and-fedora-11/
and still can't see what i'm doing wrong
Don't use root to test with. If nsswitch is not working you will need
the same UID and GID across all machines to work in the directory.
Which means user1 on server is UID & GID 600 it has to be the same on
the client also. "id" will show the user and group id numbers and
usermod and groupmod can change them. Other than that I see really
nothing in the config you have. Maybe check ls -l on the nfs share for
ACLs, file permissions for the user. Maybe someone else may spot
something in your config. Also you can run Wire Shark to check out
things for the network side and authentication.
John
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
04-21-2010, 11:47 AM
Kahlil Hodgson
Help with NFSV4 server
Hi Clint
I've got NFS4 running on F11 and your configuration looks fine to me.
I'd probably want to keep things simple while you are testing. Perhaps
cut this back to:
inf1:/ /test rw,noatime,sync,hard,intr 0 0
Running tcpdump at both ends while you try to do a directory listing may
provide some insight (which process is waiting for a response from whom)
Err grasping at straws ... you may also want to check for any old stuff
you may have in /etc/hosts.{allow,deny}.
Hope this helps,
Kal
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
04-21-2010, 12:44 PM
Tom H
Help with NFSV4 server
On Wed, Apr 21, 2010 at 1:49 AM, Clint Dilks <clintd@scms.waikato.ac.nz> wrote:
>
> I have been trying to setup an NFS v4 File Server but have come across an
> odd issue.* Mounting the /nfs4exports/share appears to be successful and the
> information displayed about partition size and free space seem correct but
> if I try to do anything inside the mounted directory the client will just
> hang.* Does anyone have any idea what I am missing??* I have try disabling
> all firewalls and selinux* but it doesn't seem to make any difference
>
> {The Server}
>
> CentOS 5.4* 64 Bit
>
> [root@inf1 /]# cat /etc/exports
> /nfs4exports
> *.scms.waikato.ac.nz(rw,insecure,sync,wdelay,no_su btree_check,no_root_squash,fsid=0,nohide)
> /nfs4exports/share
> *.scms.waikato.ac.nz(rw,insecure,sync,wdelay,no_su btree_check,no_root_squash,nohide)
>
> [root@inf1 /]# cat /etc/sysconfig/nfs
> #MOUNTD_NFS_V1="no"
> MOUNTD_NFS_V2="no"
> MOUNTD_NFS_V3="no"
> #RPCNFSDARGS="-N 2 -N 3"
> #RPCNFSDARGS="-N 4"
>
> [root@inf1 /]# cat /etc/idmapd.conf
> Verbosity = 9
> Pipefs-Directory = /var/lib/nfs/rpc_pipefs
> Domain = scms.waikato.ac.nz
> Nobody-User = nfsnobody
> Nobody-Group = nfsnobody
> Method = nsswitch
>
> [root@inf1 /]# mount -l | grep bind
> /export on /nfs4exports/share type none (rw,bind)
>
> And an ls of /nfs4exports/share on NFS Server works
>
> from /etc/fstab
> /export* /nfs4exports/share*** none*** bind*** 0 0
>
> {The Client}
>
> [root@silver ~]# cat /etc/idmapd.conf
> Verbosity = 0
> Pipefs-Directory = /var/lib/nfs/rpc_pipefs
> Domain = scms.waikato.ac.nz
> Nobody-User = nfsnobody
> Nobody-Group = nfsnobody
> Method = nsswitch
>
> From /etc/fstab
> inf1:/ /test nfs4
> auto,rw,nodev,sync,_netdev,proto=tcp,retry=10,rsiz e=32768,wsize=32768,hard,intr
> 0 0
Check showmount and rpcinfo.
Check that the uid and gid of the user accessing the mount are the
same on client and server, that idmapd is running, that there is a
sunrpc mount.
Reduce the number of options for both the export and the mount while
you are troubleshooting.
Unless my brain is not working today, your bind mount looks completely
wrong. You are setting up a bind mount of /nfs4exports/share onto
/export and not making any use of it. AFAIK, the point of the nfsv4
bind mount procedure is to export a directory (in your case,
/nfs4exports) with fsid=0 and, if you want to export another
directory, /tobeexported, which is not under /nfs4exports, you bind
mount /tobeexported onto /nfs4exports/tobeexported and can then access
is from a client as server:/tobeexported.
OT: I have not yet had to set up an nfsv4-only export, so I am curious
why you are restricting mountd to v4 but not nfsd.
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
04-27-2010, 03:40 AM
Clint Dilks
Help with NFSV4 server
On 21/04/10 23:47, Kahlil Hodgson wrote:
> Hi Clint
>
> I've got NFS4 running on F11 and your configuration looks fine to me.
>
>
>> {The Client}
>>
>> [root@silver ~]# cat /etc/idmapd.conf
>> [General]
>> ...
>> [Mapping]
>>
>> Nobody-User = nfsnobody
>> Nobody-Group = nfsnobody
>>
> You may want to check that nfsnobody is defined on your system and
> rpc.idmapd is actually running. Also the output from rpcinfo might help.
>
>
>> > From /etc/fstab
>> inf1:/ /test nfs4
>> auto,rw,nodev,sync,_netdev,proto=tcp,retry=10,rsiz e=32768,wsize=32768,hard,intr
>> 0 0
>>
> I'd probably want to keep things simple while you are testing. Perhaps
> cut this back to:
>
> inf1:/ /test rw,noatime,sync,hard,intr 0 0
>
> Running tcpdump at both ends while you try to do a directory listing may
> provide some insight (which process is waiting for a response from whom)
>
> Err grasping at straws ... you may also want to check for any old stuff
> you may have in /etc/hosts.{allow,deny}.
>
> Hope this helps,
>
> Kal
>
> _______________________________________________
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
>
Hi People,
Thanks for all the responses related to this.
To keep things simple I started from scratch. Just working on the
server and testing my mounting using the server itself and this is what
I have found
The home-test file is a test file I created inside /nfs4exports/home
so it appears that NFS v3 sees and uses a bind mounted area as you would
expect whereas NFS v4 is ignoring the bind and using the filesystem
underneath which is very strange as all the reading I have done suggests
that you now must now have bind configured for NFS v4 to work correctly.
Thank you for any insight you can offer.
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos