NFS mount issue

[VKALVEMULA]

Hi

I created one volume added to vfiler

And exported the path to one of our Unix servers and gave RW access.

And my system admin cannot do any RW on that vol.

Did anyone had same type of issue before?

[scottgelb]

Did you edit exports and exportfs from vFiler root or vfiler0? I often see the export in vfiler0 which exports but isn't accessible. Has to be in the vFiler itself. Them also check on he client showmount -e vFiler

[HARRY168]

You can check export volume's security type ~~~

[VKALVEMULA]

thanks Scott, Yu-Ming

i copied /vol/path... from exportfs file under root and pasted under test_vfiler exportfs file

and when i did exportfs -a from test_vfiler.. i am able to RW from host side.

need to do further testing.. will update here once we are done totally.

[VKALVEMULA]

question :

this test vfiler is setup in Dev/Test envt.

when i created a volume (TST_VOL) and exported to one test host (TST_EN).

we have another host (STARTER) which has access to both Prod and Dev/Test envt and sys admin was able to mount (TST_VOL) on this "STARTER" ( even tough i havent given any access to this host).

any thoughts why STARTER is able to do a Read on this TST_VOL ?

[scottgelb]

The nfs option for auto-export is set by default…so creates an automatic export. That can be turned off.

[VKALVEMULA]

is this the one you are referring to

nfs.export.auto-update       on

[scottgelb]

Correct. Whenever you create volume it automatically creates an export. And since vol create is from vfiler0, you will see it created there before assignment…it isn’t usable in vfiler0 after it is assigned to a vfiler but often it is turned off to prevent auto exports from being created.

[VKALVEMULA]

do i need to turn it off from test_vfiler prespective or vfiler0

[scottgelb]

If not needed you could do both… of to all vfilers with “vfiler run * vfiler options nfs….”

[VKALVEMULA]

i did from test_vfiler, will check with my sys admin and see whether he is able to do a read now

[scottgelb]

You need to remove the export though that was already created… that will affect new volume creation but not for existing. Then exportfs -r

[VKALVEMULA]

hi scott

i try to umount the old one and

tried to mount the same again.. i am able to do a Read on the mount point .( similar to the previous one - no change )

[scottgelb]

Does “exportfs” show a mount available? What does the host show from “showmount –e vfiler”

[VKALVEMULA]

from filer:

tst_nfs@NAS02> exportfs

/vol/tst_nfs    -sec=sys,rw,anon=0

/vol/tst_nfs_sapcd_bwt  -sec=sys,rw,root=tstbw:tstbw.xxx.com

from server:

root@starter # showmount -e tst_nfs

export list for tst_nfs:

/vol/tst_nfs            (everyone)

/vol/tst_nfs_sapcd_bwt  (everyone)

[VKALVEMULA]

not sure why its showing as "everyone" from the server side even tough i gave permissions to only tstbw

[scottgelb]

exportfs on the netapp still has it exported

[VKALVEMULA]

yes

[scottgelb]

If you exportfs -u /vol/volname then exportfs -a again does it work?  Or did you "exportfs -r" to update which will also work.

[VKALVEMULA]

i did umount from the host side and i did exportfs -r now from filer side..

will check from host side again whether its able to read.

[scottgelb · Accepted solution]

There is an rw which is to all though which might be showing it... change rw=tstbw.xxx.com to not allow write to all