NFS3 versus NFS4 Shared Storage (nobody:nobody)


            Product Line:  VERDE



            ISSUE:  


            When configuring the VERDE shared storage, where the /home/vb-verde is stored, the subject directory and subsequent directories are owned by nobody:nobody and all VERDE activity fails..

            NFS v4 mount may not allow non-root read/write access. However, that same export can be made usable by mounting as v3 changing ownership then re-mounting as v3.

             

            Details:


            [root@rhel64 home]# mount
            <snip>
            172.16.1.234:/vol/vol0/data/nfstest2 on /home/nfstest2 type nfs (rw,noatime,nodiratime,nfsvers=4,addr=172.16.1.234,clientaddr=172.16.100.34)

            # NFS v4 mount is owned by nobody:nobody
            [root@rhel64 home]# ls -la /home/nfstest2
            total 8
            drwxr-xr-x 2 nobody nobody 4096 Dec 11 11:33 .
            drwxr-xr-x 6 root   root   4096 Dec 11 11:41 ..

            # Change owner to vb-verde fails with "Invalid argument"
            [root@rhel64 home]# chown vb-verde.vb-verde /home/nfstest2
            chown: changing ownership of `/home/nfstest2': Invalid argument

            # vb-verde cannot write to the NFS mount
            [root@rhel64 home]# su - vb-verde
            -bash-4.1$ touch /home/nfstest2/testfile
            touch: cannot touch `/home/nfstest2/testfile': Permission denied
            -bash-4.1$ exit
            logout

            # Now re-mount same export as NFS v3
            [root@rhel64 home]# umount /home/nfstest2
            [root@rhel64 home]# mount -t nfs -o rw,nfsvers=3 172.16.1.234:/vol/vol0/data/nfstest2 /home/nfstest2

            # Change owner to vb-verde succeeds using NFS v3
            [root@rhel64 home]# chown vb-verde.vb-verde /home/nfstest2
            [root@rhel64 home]# ls -la /home/nfstest2
            total 8
            drwxr-xr-x 2 vb-verde vb-verde 4096 Dec 11  2013 .
            drwxr-xr-x 6 root     root     4096 Dec 11 11:41 ..

            # vb-verde can now write to mount point
            [root@rhel64 home]# su - vb-verde
            -bash-4.1$ touch /home/nfstest2/testfile
            -bash-4.1$ exit
            logout
            [root@rhel64 home]# ls -la /home/nfstest2
            total 8
            drwxr-xr-x 2 vb-verde vb-verde 4096 Dec 11  2013 .
            drwxr-xr-x 6 root     root     4096 Dec 11 11:41 ..
            -rw-rw-r-- 1 vb-verde vb-verde    0 Dec 11  2013 testfile

            # Now remount again as NFS v4
            [root@rhel64 home]# umount /home/nfstest2
            [root@rhel64 home]# mount -t nfs -o rw,nfsvers=4 172.16.1.234:/vol/vol0/data/nfstest2 /home/nfstest2

            # Again mount is owned by nobody:nobody
            [root@rhel64 home]# ls -la /home/nfstest2
            total 8
            drwxr-xr-x 2 nobody nobody 4096 Dec 11  2013 .
            drwxr-xr-x 6 root   root   4096 Dec 11 11:41 ..
            -rw-rw-r-- 1 nobody nobody    0 Dec 11  2013 testfile

            # *However* vb-verde has full read/write permission now
            [root@rhel64 home]# su - vb-verde
            -bash-4.1$ touch /home/nfstest2/testfile2
            -bash-4.1$ ls -la /home/nfstest2
            total 8
            drwxr-xr-x 2 nobody nobody 4096 Dec 11 12:33 .
            drwxr-xr-x 6 root   root   4096 Dec 11 11:41 ..
            -rw-rw-r-- 1 nobody nobody    0 Dec 11 12:31 testfile
            -rw-rw-r-- 1 nobody nobody    0 Dec 11 12:33 testfile2
            -bash-4.1$


            Updated: 02 Apr 2018 11:00 AM
            Helpful?  
            Help us to make this article better
            0 0