Subscribe
Accepted Solution

Strange NFS mount issue

I have a strange situation here at the customer site that I have never seen before and I am hoping someone can point me in the right direction.

 

I have a server that is able to mount a volume via NFSv3 from a vserver.  When I try to mount another volume from the same vserver via NFSv3 I get this message:

 

[root@fgtd-333333-aspadavecchia-db001 mnt]# mount -t nfs -v -o rw,nointr,noacl,noatime,rsize=32768,wsize=32768,defaults,vers=3,tcp,mountproto=udp,bg,hard,nolock vsnfsbbl.bbcs1.trcl1va2.mhint:/bbl_nfs_td1_333333_aspadavecchia_dbo/db001 /home/oracle

mount.nfs: trying text-based options 'nointr,noacl,rsize=32768,wsize=32768,vers=3,tcp,mountproto=udp,bg,hard,nolock,addr=10.8.236.4'

mount.nfs: prog 100003, trying vers=3, prot=6

mount.nfs: trying 10.8.236.4 prog 100003 vers 3 prot TCP port 2049

mount.nfs: prog 100005, trying vers=3, prot=17

mount.nfs: trying 10.8.236.4 prog 100005 vers 3 prot UDP port 635

mount.nfs: mount(2): No such file or directory

mount.nfs: mounting vsnfsbbl.bbcs1.trcl1va2.mhint:/bbl_nfs_td1_333333_aspadavecchia_dbo/db001 failed, reason given by server: No such file or directory

 

 

If I mount using no options, the mount is successful but only with NFSv4

 

[root@fgtd-333333-aspadavecchia-db001 mnt]# mount -v vsnfsbbl.bbcs1.trcl1va2.mhint:/bbl_nfs_td1_333333_aspadavecchia_dbo/db001 /home/oracle

mount: no type was given - I'll assume nfs because of the colon

mount.nfs: timeout set for Wed Jul 27 21:04:10 2016

mount.nfs: trying text-based options 'vers=4,addr=10.8.236.5,clientaddr=10.8.224.122'

vsnfsbbl.bbcs1.trcl1va2.mhint:/bbl_nfs_td1_333333_aspadavecchia_dbo/db001 on /home/oracle type nfs (rw)

 

Here is the volume that we can mount via NFSv3:

 

[root@fgtd-333333-aspadavecchia-db001 mnt]# mount -t nfs -v -o vers=3 vsnfsbbl.bbcs1.trcl1va2.mhint:/asp/asp /mnt/asp

mount.nfs: timeout set for Wed Jul 27 21:09:59 2016

mount.nfs: trying text-based options 'vers=3,addr=10.8.236.7'

mount.nfs: prog 100003, trying vers=3, prot=6

mount.nfs: trying 10.8.236.7 prog 100003 vers 3 prot TCP port 2049

mount.nfs: prog 100005, trying vers=3, prot=17

mount.nfs: trying 10.8.236.7 prog 100005 vers 3 prot UDP port 635

vsnfsbbl.bbcs1.trcl1va2.mhint:/asp/asp on /mnt/asp type nfs (rw,vers=3)

 

I even tried using the same export policy that the /asp volume uses.

 

 

Re: Strange NFS mount issue

UPDATE:  I have found the issue and fix for this problem.

 

Turns out that the LS mirror of the vserver root volume was causing the issue.  The root volume LS mirror had not been updated in quite a long time.  This causes an issue when trying to mount new volumes.  Once I updated the mirror the issue was gone.

 

https://kb.netapp.com/support/index?page=content&id=3013933

 

Make sure you LS mirrors are updated regularly.

 

James