As far as I can tell, you are trying to mount /export/orabak but you actually mounted /orabak:
# mkdir /orabak # mount -t nfs4 192.168.10.1:/orabak /orabak # df -k /orabak Filesystem 1K-blocks Used Available Use% Mounted on 192.168.10.1:/orabak 16251840 2172704 13240288 15% /orabak Maybe you have a link on the host server from /export to /orabak? Kevin -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Robin Garner Sent: Sunday, August 30, 2009 11:39 PM To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: [rhelv5-list] NFS4 serves the wrong filesystem I'm having a very odd problem trying to set up nfs v4 on a pair of RHEL 5.4 beta boxes. The server node is mounting the shared filesystem from a SAN, managed using dm-multipath. We have a private network for cluster/NFS traffic. The server is setup as follows: # mkdir /export/orabak # mount /dev/mapper/orabakp1 /export/orabak # cat /etc/exports /export 192.168.10.0/24(rw,no_root_squash,fsid=0) /export/orabak 192.168.10.0/24(rw,no_root_squash) # exportfs -v /export/orabak 192.168.10.0/24(rw,wdelay,no_root_squash,no_subtree_check,anonuid=65534, anongid=65534) /export 192.168.10.0/24(rw,wdelay,no_root_squash,no_subtree_check,fsid=0,anonuid =65534,anongid=65534) # showmount -e localhost Export list for localhost: /export 192.168.10.0/24 /export/orabak 192.168.10.0/24 # df -k /export/orabak Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/orabakp1 154816488 192072 146760200 1% /export/orabak # ls -l /export/orabak total 16 drwx------ 2 root root 16384 Aug 31 15:40 lost+found -rw-r--r-- 1 root root 0 Aug 31 15:41 this.is.orabak.on.node1 So far so good. On the client, # showmount -e 192.168.10.1 Export list for 192.168.10.1: /export 192.168.10.0/24 /export/orabak 192.168.10.0/24 # mkdir /orabak # mount -t nfs4 192.168.10.1:/orabak /orabak # df -k /orabak Filesystem 1K-blocks Used Available Use% Mounted on 192.168.10.1:/orabak 16251840 2172704 13240288 15% /orabak So far so good, except that the size of the disk isn't right. An ls confirms that something's odd: # ls -l /orabak total 0 # touch /orabak/this.is.orabak.on.ldora2 # ls -l /orabak total 0 -rw-r--r-- 1 root root 0 Aug 31 16:00 this.is.orabak.on.node2 Now, if I go back to node1, # ls -l /export/orabak/ total 16 drwx------ 2 root root 16384 Aug 31 15:40 lost+found -rw-r--r-- 1 root root 0 Aug 31 15:41 this.is.orabak.on.node1 The file I created from node2 definitely isn't there # service nfs stop # umount /export/orabak/ # ls -l /export/orabak total 0 -rw-r--r-- 1 root root 0 Aug 31 16:00 this.is.orabak.on.ldora2 This is where it went. So the nfs4 daemon is serving up the underlying mountpoint, not the filesystem mounted on it. Does anyone know what's going on ? Or how I might diagnose it ? Robin Garner Linux Administrator Southern Cross University _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
