Note I have cases open with Redhat and Netapp, but was curious if other people have also seen inconsistent mount attributes (ro/rw) when mounting RHEL5 client vs. Netapp 7.2 Ontap.

---+ System environment

[greg@adcgar04 greg]$ uname -a Linux adcgar04 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:14 EST 2007 x86_64 unknown unknown GNU/Linux

[greg@adcgar04 greg]$ rpm -qa | grep nfs-utils nfs-utils-1.0.9-16.el5 nfs-utils-lib-1.0.8-7.2 nfs-utils-lib-devel-1.0.8-7.2 nfs-utils-lib-1.0.8-7.2 nfs-utils-lib-devel-1.0.8-7.2

[greg@adcgar04 greg]$ mount -V mount (util-linux 2.13-pre7)

---+ NFS server (Netapp) environment

[greg@apathy greg]$ sudo rsh eng version NetApp Release 7.2P4: Tue Nov 28 02:55:54 PST 2006

---++ NFS export file entry

[greg@apathy greg]$ sudo rsh eng exportfs | grep pandora

/vol/vol4/pandora -sec=sys,ro,rw=@volexport-pandora,root=@volexport-pandora,anon=4058

---++ netgroup member (for export file entry above)

[greg@apathy greg]$ show_netgroup volexport-pandora | grep adcgar adcgar04.amd.com

---+ Demonstration of inconsistent ro/rw mount reporting

[root@adcgar04 /]# mount eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2

[root@adcgar04 /]# mount -v | grep mnt2 eng:/vol/vol4/pandora/pandora-k26_g25_64-2 on /mnt2 type nfs (rw,addr=163.181.34.137)

[root@adcgar04 /]# cat /proc/mounts | grep mnt2 eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2 nfs ro,vers=3,rsize=65536,wsize=65536,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=eng

0 0

[root@adcgar04 /]# cd /mnt2/

[root@adcgar04 mnt2]# touch asdf touch: cannot touch `asdf': Read-only file system

---+ Discussion

---++Linux (RHEL3/4) NFS servers that have similiar exportfs options

/tmp *(ro,anonuid=4058) @volexport-pandora(rw,no_root_squash)

do not cause the inconsistent behavior between mount -v and /proc/mounts (and it is mounted rw as expected on the client).

---++ A reply from NetApp had this info:

Starting with ONTAP 7.2.1 onward, ONTAP will display the "most pessimistic" permissions to NFSv3 and NFSv4 clients. NFSv2 clients will see permissions the same way as in previous releases of ONTAP, i.e. the "most optimistic" permissions.

And mounting using NFS v2 (instead of v3) does give us the expected rw/rw consistency and ability.

---++ So now what?

Should the linux mount -v and cat /proc/mounts be consistent with what is actually happening?

Should netapp exports syntax handle a wildcard ro and a netgroup rw?

Comments and feedback welcome.

Thanks,

--Greg