I can try to play around with the idmapd.conf and set the fsid=0 option. What bugs me, though, is that neither option is enabled on the SL6/RHES6 server and I am able to mount via nfs4:
[root@centos sysconfig]# nfsstat Server rpc stats: calls badcalls badauth badclnt xdrcall 154 0 0 0 0
Server nfs v3: null getattr setattr lookup access readlink 28 36% 27 35% 0 0% 0 0% 0 0% 0 0% read write create mkdir symlink mknod 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% remove rmdir rename link readdir readdirplus 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% fsstat fsinfo pathconf commit 3 3% 16 20% 3 3% 0 0%
Server nfs v4: null compound 32 45% 38 54%
Server nfs v4 operations: op0-unused op1-unused op2-future access close commit 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% create delegpurge delegreturn getattr getfh link 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% lock lockt locku lookup lookup_root nverify 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% open openattr open_conf open_dgrd putfh putpubfh 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% putrootfh read readdir readlink remove rename 35 92% 0 0% 0 0% 0 0% 0 0% 0 0% renew restorefh savefh secinfo setattr setcltid 1 2% 0 0% 0 0% 0 0% 0 0% 1 2% setcltidconf verify write rellockowner 1 2% 0 0% 0 0% 0 0%
Client rpc stats: calls retrans authrefrsh 38 0 0
Client nfs v4: null read write commit open open_conf 0 0% 0 0% 0 0% 0 0% 1 2% 1 2% open_noat open_dgrd close setattr fsinfo renew 0 0% 0 0% 1 2% 1 2% 4 11% 0 0% setclntid confirm lock lockt locku access 1 2% 1 2% 0 0% 0 0% 0 0% 2 5% getattr lookup lookup_root remove rename link 7 19% 5 13% 2 5% 0 0% 0 0% 0 0% symlink create pathconf statfs readlink readdir 0 0% 0 0% 0 0% 2 5% 0 0% 2 5% server_caps delegreturn 6 16% 0
root@centos sysconfig]# cat /etc/mtab /dev/sda6 / ext3 rw 0 0 proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 devpts /dev/pts devpts rw,gid=5,mode=620 0 0 /dev/sda8 /home ext3 rw 0 0 /dev/sda5 /usr ext3 rw 0 0 /dev/sda3 /opt ext3 rw 0 0 /dev/sda2 /var ext3 rw 0 0 /dev/sda1 /boot ext3 rw 0 0 tmpfs /dev/shm tmpfs rw 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0 sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0 nfsd /proc/fs/nfsd nfsd rw 0 0 /opt/company_data /exports/company_data none rw,bind 0 0 192.168.15.100:/opt/company_data /mnt nfs4 rw,addr=192.168.15.100 0 0
(Of course, it could be that SL6 did things a little differently with their distro's implementation of NFS4, but I doubt it).
On May 30, 2011, at 10:29 PM, Tom H wrote:
On Mon, May 30, 2011 at 9:31 PM, RILINDO FOSTER rilindo@me.com wrote:
After getting a reasonably configured NFS4 setup working on my Scientific Linux server, I spent a majority of my evening trying to do the same with my Centos 5 box, with fruitless results. Most attempts to mount that server returns the following message:
[root@sl01 log]# mount -t nfs4 192.168.15.200:/opt/company_data /mnt mount.nfs4: Operation not permitted
As nearest as I can tell, I was able to setup the ports correctly in /etc/sysconfig/nfs
[root@centos sysconfig]# grep -v # nfs RQUOTAD_PORT=875 LOCKD_TCPPORT=32803 LOCKD_UDPPORT=32769 MOUNTD_PORT=892 STATD_PORT=662
[root@centos sysconfig]# rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 662 status 100024 1 tcp 662 status 100011 1 udp 875 rquotad 100011 2 udp 875 rquotad 100011 1 tcp 875 rquotad 100011 2 tcp 875 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100021 1 udp 32769 nlockmgr 100021 3 udp 32769 nlockmgr 100021 4 udp 32769 nlockmgr 100021 1 tcp 32803 nlockmgr 100021 3 tcp 32803 nlockmgr 100021 4 tcp 32803 nlockmgr 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 892 mountd 100005 1 tcp 892 mountd 100005 2 udp 892 mountd 100005 2 tcp 892 mountd 100005 3 udp 892 mountd 100005 3 tcp 892 mountd
And services are running:
[root@centos sysconfig]# service nfs status rpc.mountd (pid 6321) is running... nfsd (pid 6318 6317 6316 6315 6314 6313 6312 6311) is running... rpc.rquotad (pid 6306) is running... [root@centos sysconfig]# service nfslock status rpc.statd (pid 6248) is running... [root@centos sysconfig]# service portmap status portmap (pid 6210) is running...
And firewall is open both ways:
[root@centos sysconfig]# iptables -n -L | grep -E '(2049|111|32759|32803|662|875|892)' ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:111 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:2049 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:2049 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:875 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:875 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:875 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:892 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:662 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:32803 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:32803 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:662 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:892 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:111 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:111 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:111 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:2049 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:2049 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:32803 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:32803 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:662 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:662 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:892 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:875 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:875
I am about to mount via NFS3, so that part I know works.
Is there a known problem with NFS4 on Centos (or Red Hat) 5? Or am I missing something someplace?
Are the values of "Domain" in "/etc/idmapd.conf" the same on the client and the server?
FYI: For nfsv4, there's no need to have any ports other than 111 and 2049.
(Are you using "fsid=0" as an option?) _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos