Debug failed mount: No such file or directory

[PatrikOsgnach]

Hi all, I recently inherited an already configured AFF-A300. It already has some volumes, exported via NFS3 and they all work fine.

Today I tried to add a new volume via the Ontap system manager, but the mount fails:

# mount -v -t nfs vrc01n01b:/proj_rfip_hki /root/hki
mount.nfs: timeout set for Fri Dec 20 19:21:29 2024
mount.nfs: trying text-based options 'vers=4,addr=10.217.231.21,clientaddr=10.217.231.88'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=10.217.231.21'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.217.231.21 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.217.231.21 prog 100005 vers 3 prot UDP port 635
mount.nfs: mount(2): No such file or directory
mount.nfs: mounting vrc01n01b:/proj_rfip_hki failed, reason given by server: No such file or directory

To check the most obvious reasons: 

> volume show -vserver vrcv01a -fields volume,node,junction-path,policy
vserver volume    policy                  junction-path node      
------- --------- ----------------------- ------------- ---------
vrcv01a proj_rfip_hki 
                  clients                 /proj_rfip_hki 
                                                        vrc01n01b

> vserver export-policy check-access -vserver vrcv01a -client-ip 10.217.231.88 -volume proj_rfip_hki -authentication-method sys -protocol nfs3 -access-type read
                                Policy    Policy     Rule             Security
Path                 Policy     Owner     Owner Type Index Access     Style
-------------------- ---------- --------- ---------- ---- ---------- ----------
/                    default    vrcv01a_rootvol 
                                          volume        2 read       unix
/proj_rfip_hki       clients    proj_rfip_hki 
                                          volume        2 read       unix

>  export-policy access-cache show -node vrc01n01b -vserver vrcv01a -policy clients -address 10.217.231.88

                                        Node: vrc01n01b
                                     Vserver: vrcv01a
                                 Policy Name: clients
                                  IP Address: 10.217.231.88
                    Access Cache Entry Flags: has-usable-data
                                 Result Code: 0
                 First Unresolved Rule Index: -
                      Unresolved Clientmatch: -
              Number of Matched Policy Rules: 1
         List of Matched Policy Rule Indexes: 2
                                Age of Entry: 741s
                 Access Cache Entry Polarity: positive
Time Elapsed since Last Use for Access Check: 407s
      Time Elapsed since Last Update Attempt: 741s
               Result of Last Update Attempt: 0
                List of Client Match Strings: 10.217.231.0/25

From the client:

# showmount -e vrc01n01b
Export list for vrc01n01b:
/proj_rfip_hki                          (everyone)

So, volume is there, it is mounted, it has an export policy and the client is allowed to mount.

What am I missing? Is there anything like "exportfs -r" that I have to run?

[PatrikOsgnach]

Accorting to the ONTAP System Manager, I should be able to mount the volume from either 

10.217.231.20:/proj_rfip_hki or 10.217.231.21:/proj_rfip_hki ... neither work.

Shouldn't the junction path be created automatically? The mount command seems to work (or at least it doesn't give any explicit error)

If there is no mkdir command in the CLI interface, shall I mount the root of the SVM on a linux host and create the mount point?

[TMACMD]

I’ll send some directions later when I’m at a computer

[PatrikOsgnach]

Hi, did you find anything?

[PatrikOsgnach]

> net int show -vserver vrcv01a -lif vrc01n01b-1 -fields service-policy 
  (network interface show)
vserver lif         service-policy    
------- ----------- ----------------- 
vrcv01a vrc01n01b-1 custom-data-48468
> net int service-policy show -vserver vrcv01a -policy custom-data-48468
  (network interface service-policy show)

                   Vserver: vrcv01a
               Policy Name: custom-data-48468
         Included Services: data-core, data-nfs, data-fpolicy-client,
                            management-dns-client, management-ad-client,
                            management-ldap-client, management-nis-client,
                            data-dns-server, backup-ndmp-control
Service: Allowed Addresses: data-core: 0.0.0.0/0
                            data-nfs: 0.0.0.0/0
                            data-fpolicy-client: 0.0.0.0/0
                            management-dns-client: 0.0.0.0/0
                            management-ad-client: 0.0.0.0/0
                            management-ldap-client: 0.0.0.0/0
                            management-nis-client: 0.0.0.0/0
                            data-dns-server: 0.0.0.0/0
                            backup-ndmp-control: 0.0.0.0/0

Now... what happens if the path where the volume should be mounted does not exist? Can I manually create it?

I can mount all other shares, except this one

[PatrikOsgnach · Accepted solution]

So, now I finally found the real issue and the solution can be found here https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NFS_mount_error__failed_reason_given_by_server__No_such_file_or_directory

The command that fixed the problem is

snapmirror update-ls-set -source-path <vserver_name>:<volume_name>

where volume_name is the name of the SVM root volume