NFS mount -

Rick Stevens ricks at alldigital.com
Fri Nov 14 21:32:30 UTC 2014


On 11/14/2014 12:12 PM, Bob Goodwin - Zuni, Virginia, USA issued this
missive:
> 
> I have a problem connecting this Fedora-20 computer with an NFS server.
> I have just set up the server on Scientific Linux 7.
> 
> The mount command:
> 
> [root at box10 bobg]# mount 192.168.1.48:/mnt/nasdata  /mnt/box48/

You have several problems. First, the NFS server is set up to export

	/nfs4exports
	/nfs4exports/data
	/nfs4exports/home

It is NOT exporting /mnt/nasdata. You can try "showmount -e" on the
NFS server to see what it's actually exporting. I think you'll find the
things being exported all start with /nfs4exports. If that's the case,
try:

	mount 192.168.1.48:/nfs4exports /mnt/box48

See my other comments below.

> Does nothing until it eventually times out. I can ssh into the server
> and see all the files. I tried to configure it to be nearly the same as
> another NFS server that has been working well.
> 
> [bobg at box48 ~]$ cat /etc/exports
> #
> #    /etc/exports
> 
> /nfs4exports
> 192.168.1.0/24(ro,sync,insecure,no_root_squash,no_subtree_check,fsid=0)
> 
> /nfs4exports/data
> 192.168.1.0/24(rw,sync,insecure,no_root_squash,no_subtree_check)
> 
> /nfs4exports/home
> 192.168.1.0/24(rw,sync,insecure,no_root_squash,no_subtree_check)
> 
> 
> [bobg at box48 ~]$ cat /etc/fstab
> 
> #
> # /etc/fstab
> # Created by anaconda on Fri Nov 14 16:24:27 2014
> #
> # Accessible filesystems, by reference, are maintained under '/dev/disk'
> # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
> #
> UUID=edf0c0db-d48a-46da-81b3-ef6c7b502175 / xfs     defaults        1 1
> UUID=ae08aa95-4ffc-4ac4-a434-60909636c0bf /boot xfs     defaults        1 2
> UUID=f3aeadd2-70bc-4f45-b6d6-2f96f602871e /home xfs     defaults        1 2
> UUID=3f57869c-eca7-4196-a28f-698acf3c752c swap swap    defaults        0 0
> 
> # bind mounts
> 
> /home/data    nfs4exports/data    none    rw,bind    0 0
> 
> /home/home    nfs4exports/home    none    rw,bind    0 0

Looking at your bindmounts, the actual mountpoints that you're using
aren't absolute. I think you want:

	/home/data    /nfs4exports/data    none    rw,bind    0 0
	/home/home    /nfs4exports/home    none    rw,bind    0 0

And ensure that the "/nfs4exports", "/nfs4exports/data" and
"/nfs4exports/home" directories all exist BEFORE you execute the
bindmount.

> I have been referring to the Fedora Project NFS guide but apparently I
> am missing something. I tried systemctl stop iptables on the server, no
> change. I routinely mount the other NFS so I assume the problem is not
> in "Firewalld."
> 
> One difference is that the server in question has two identical drives
> configured Raid1. Apparently XFS is preferred or required, I'm nor sure
> but Anaconda kept changing ext4 to xfs so I assumed they know better
> than I do?
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks at alldigital.com -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-   Which is worse: ignorance or apathy?  I don't know.  Who cares?  -
----------------------------------------------------------------------


More information about the users mailing list