NFS4 problems -

[Bob Goodwin - Zuni, Virginia, USA]

On 03/12/12 15:46, Bob Goodwin - Zuni, Virginia, USA wrote:
> On 03/12/12 15:27, Ed Greshko wrote:
>> 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.
>
>    Confusion I'm sure. I did try "defaults,rw,user" it had no effecto 
> on mounting at start up so I put it back as you see it.
>
>>
>>
>> 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
>
>        [bobg at box7 ~]$ ssh bobg at box8
>        bobg at box8's password:
>        Last login: Mon Dec  3 09:35:47 2012 from box7
>        Could not chdir to home directory /home/bobg: No such file or
>        directory
>        -bash-4.1$ ll /
>        total 98
>        dr-xr-xr-x.   2 root root  4096 Nov 28 05:11 bin
>        dr-xr-xr-x.   6 root root  1024 Nov 28 04:45 boot
>        drwxr-xr-x.  20 root root  3720 Aug  4  2009 dev
>        drwxr-xr-x.  99 root root  4096 Dec  1 12:47 etc
>        drwxrwxrwx.   6 root root  4096 Dec  1 14:10 home
>        dr-xr-xr-x.  10 root root  4096 Feb 16  2012 lib
>        dr-xr-xr-x.  10 root root 12288 Nov 28 05:11 lib64
>        drwx------.   2 root root 16384 Feb 16  2012 lost+found
>        drwxr-xr-x.   2 root root  4096 Jul 20  2011 media
>        drwxr-xr-x.   3 root root  4096 Dec  1 11:18 mnt
>        drwxrwxrwt.   4 root root  4096 Dec  1 12:21 nfs4exports
>        drwxrwxrwx.  11 root root  4096 Dec  1 11:18 nfsexports
>        drwxr-xr-x.   2 root root  4096 Jul 20  2011 opt
>        dr-xr-xr-x. 247 root root     0 Aug  4  2009 proc
>        dr-xr-x---.   6 root root  4096 Dec  1 12:19 root
>        dr-xr-xr-x.   2 root root 12288 Nov 28 05:11 sbin
>        drwxr-xr-x.   7 root root     0 Aug  4  2009 selinux
>        drwxr-xr-x.   2 root root  4096 Jul 20  2011 srv
>        drwxr-xr-x.  13 root root     0 Aug  4  2009 sys
>        drwxrwxrwt.  13 root root  4096 Dec  3 06:08 tmp
>        drwxr-xr-x.  13 root root  4096 Feb 16  2012 usr
>        drwxr-xr-x.  18 root root  4096 Feb 16  2012 var
>        -bash-4.1$

    I realize there is stuff that can be removed from "/" but don't
    think it is causing my problem.

>
>>
>>
>>> >    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 at 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....

    "Because "bind" in in your fstab on the client"  Not sure what this
    means?

    Bob

-- 
http://www.qrz.com/db/W2BOD

box7