NFSv4

[Raymond Pittigher]

On 06/18/2012 08:17 AM, Ed Greshko wrote:
> Raymond Pittigher <raymond.pittigher at exelisinc.com> wrote:
>
>> the fstab is set at defaults. i am guessing something has changed with
>> the nfs-utils package maybe with nis?
>>
>> [root at dhcp5169 ~]# getfacl /users/zbarak/
>> getfacl: Removing leading '/' from absolute path names
>> # file: users/zbarak/
>> # owner: 4294967294
>> # group: 4294967294
>> user::rwx
>> group::---
>> other::---
>>
>> [root at dhcp5169 ~]# getfacl /users
>> getfacl: Removing leading '/' from absolute path names
>> # file: users
>> # owner: root
>> # group: root
>> user::rwx
>> group::r-x
>> other::r-x
>>
>> [root at dhcp5169 ~]# cat /etc/fstab
>>
>> #
>> # /etc/fstab
>> # Created by anaconda on Mon Jun 11 03:08:30 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
>> #
>> /dev/mapper/vg_dhcp5169-lv_root /                       ext4
>> defaults        1 1
>> UUID=bde99a9d-779d-4211-b3e1-808b62ed0195 /boot                   ext4
>>   defaults        1 2
>> /dev/mapper/vg_dhcp5169-lv_swap swap                    swap
>> defaults        0 0
>> 172.30.5.244:/users	/users				nfs4	defaults	0 0
>>
>
> Well that all looks good. I know there have been changes to nfs-utils. One change involved the idmap service and no longer needing to run it on the client. But I just wrote a bugzilla against it for random mounts failing at boot time. Since I don't see mapping problems I'd be more suspect of NIS.
>
>
But with NFSv4 as NFSv3 looks and works fine on F17.