On 12/04/2012 12:56 AM, Bob Goodwin - Zuni, Virginia, USA wrote:
cat time again.....
[root@box7 bobg]# cat /etc/fstab
This is the CLIENT.... Yes?
#
# /etc/fstab
# Created by anaconda on Tue Aug 7 08:37:16 2012
#
# 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=4ce86523-2d45-4174-85e9-fd298e4516c8 / ext4 defaults 1 1
UUID=1a9d0937-2247-4cbc-b27d-4775c7453dba /boot ext4 defaults 1 2
UUID=96a666e2-73ac-4f5f-98bc-4a6a9383491f /home ext4 defaults 1 2
UUID=9cb5a7e0-c752-4563-b7f5-663980e090e3 swap swap defaults 0 0
192.168.1.8:/nfs4exports/ /mnt/BOX8 nfs4 rw,bind 0 0
192.168.1.8:/home/ /mnt/HOME1/ nfs4 rw,bind 0 0
192.168.1.8:/data/ /mnt/DATA1 nfs4 rw,bind 0 0
Why do you have "bind" listed in the options for a remote mount? It should be
defaults,rw,user just like you have for 192.168.1.48.
Just to make sure I am understanding what you've done....
On 192.168.1.8 (the server) show the output of....
cd /
ls -l
192.168.1.48:/SRVR1 /mnt/BOX48 nfs4
defaults,rw,user 0 0
The server box48 mounts during the boot process, box8 does not. I see the following lines
in "mount":
/dev/sdb3 on /mnt/BOX8 type ext4 (rw,relatime,seclabel,data=ordered)
/dev/sdb3 on /mnt/HOME1 type ext4 (rw,relatime,seclabel,data=ordered)
/dev/sdb3 on /mnt/DATA1 type ext4 (rw,relatime,seclabel,data=ordered)
192.168.1.48://SRVR1 on /mnt/BOX48 type nfs4
(rw,nosuid,nodev,noexec,relatime,vers=4.0,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.7,local_lock=none,addr=192.168.1.48)
gvfs-fuse-daemon on /run/user/bobg/gvfs type fuse.gvfs-fuse-daemon
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
Which raises the question why are the non-working mounts shown as /dev/sdbx while the one
that mounts [box48] does not? Then after mounting manually with "[root@box7 bobg]#
mount 192.168.1.8:/home/ /mnt/HOME1/" mount shows:
192.168.1.8:/home on /mnt/HOME1 type nfs4
(rw,relatime,vers=4.0,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.7,local_lock=none,addr=192.168.1.8)
Any thoughts? I am getting nowhere on it.
Because "bind" in in your fstab on the client....
--
Programming today is a race between software engineers striving to build bigger and better
idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far,
the Universe is winning. -- Rick Cook, The Wizardry Compiled