Subscribe
Accepted Solution

NFS mount issue: volume can mount but not the folder underneath

Our Linux admin can mount the volume and see the folders:

 

mount dcnas02-nfs:/vol/livesiteprodslgdc /mnt
[root@slglvmo7 ~]# ll /mnt
total 52
drwxrwxrwx 12 nobody nobody  4096 Mar 23  2017 cache
drwxrwxr-x   8  nobody nobody   40960 Nov 13 16:45 content
drwxrwxr-x   3  nobody nobody   4096 Jul 27  2016 library

 

However, he cannot mount the folder:

 

umount /mnt
[root@slglvmo7 ~]# mount dcnas02-nfs:/vol/livesiteprodslgdc/content   /mnt
mount.nfs: access denied by server while mounting dcnas02-nfs:/vol/livesiteprodslgdc/content

 

 

From my perspective we only export the volume and the export rules apply to this:

 

GRCLNAS::> export-policy  rule show -vserver dcnas02-nfs  -policyname transition_export_policy_15
             Policy          Rule    Access   Client                RO
Vserver      Name            Index   Protocol Match                 Rule
------------ --------------- ------  -------- --------------------- ---------
dcnas02-nfs  transition_export_policy_15
                             1       nfs      slglvmf5.internal.    sys
                                              xxxxx.com
dcnas02-nfs  transition_export_policy_15
                             2       nfs      0.0.0.0/0             sys
dcnas02-nfs  transition_export_policy_15
                             3       cifs     0.0.0.0/0             any

 

cheers rob

 

 

 

 

 

Re: NFS mount issue: volume can mount but not the folder underneath

The first command allows the volume to be mounted but can you actually access those subfolders once mounted i.e. Cd into them? What security style is set on the volume? Can you access these same volumes through a cifs share and if so does access work there?

 

If it a permissions issue then the following command usually helps: vserver security file-directory show -vserver <vserver name> -path <path>

Re: NFS mount issue: volume can mount but not the folder underneath

Hi, thanks for your reaponse. I subsequently realised that the volume had qtrees with export policies applied to them:

Once I altered the applicable export policy the Linux guys were able to access the folder.

 

thanks Rob

 

 

EG

 

Vserver    Volume        Qtree        Style        Oplocks   Status
---------- ------------- ------------ ------------ --------- --------
dcnas02-nfs
           livesiteprodslgdc
                         ""           unix         enable    normal
dcnas02-nfs
           livesiteprodslgdc
                         cache        unix         enable    normal
dcnas02-nfs
           livesiteprodslgdc
                         content      unix         enable    normal
dcnas02-nfs
           livesiteprodslgdc
                         library      unix         enable    normal

 

 

Vserver Name: dcnas02-nfs
                       Volume Name: livesiteprodslgdc
                        Qtree Name: content
  Actual (Non-Junction) Qtree Path: /vol/livesiteprodslgdc/content
                    Security Style: unix
                       Oplock Mode: enable
                  Unix Permissions: ---rwxrwxr-x
                          Qtree Id: 2
                      Qtree Status: normal
                     Export Policy: transition_export_policy_33