ONTAP Discussions

mount sporadicaly timeout at boot time

grocanar
248 Views

Hi

On my RHEL7 some NFS share sporadicaly time out during the mounting phase. 
It s not always the same share
if i connect on the computer if i mount manually it works like a charm. 

I guess it s kind of performance problem as i m mount numerous NFs share ( more than 100 ) .

 

025-11-14T00:20:48+01:00 inti022.cnrgh.fr systemd: Mounting /env/export/v_bex...
2025-11-14T00:22:18+01:00 inti022.cnrgh.fr systemd: env-export-v_bex.mount mounting timed out. Stopping.
2025-11-14T00:22:18+01:00 inti022.cnrgh.fr systemd: env-export-v_bex.mount mount process exited, code=killed status=15
2025-11-14T00:22:18+01:00 inti022.cnrgh.fr systemd: Failed to mount /env/export/v_bex.

I have put the following options

timeo=600,retrans=2

 

Does someone have some hints to debug further 

2 REPLIES 2

parisi
206 Views

Sounds like a boot storm scenario, where you might be exhausting node resources when you attempt so many mounts at a time.

 

You could look at the event log in the CLI of ONTAP (event log show) and see if you're getting any connection errors or NFS errors. 

 

If this is NFSv3, try adding "tcp" to the mount options to ensure that the connections are closed properly when mounts occur. Some of the ancillary stuff in NFS uses UDP, which will time out on its own in the server, but will eat up connection resources in the meantime.

 

If this is NFSv4, see if you're hitting any storepool limits:

NFSv4 Storepool - Resolution guide - NetApp Knowledge Base

 

Also, as a best practice, set up at least 1 IP address per node in the SVM, set up a DNS round robin (ie, A/AAAA records with the same hostname but different IP addresses) and then have the mounts try the FQDN to round robin those connections.

grocanar
186 Views

Thanks for your interest in my post.
I definitalely agree that is reach some kind of ressource exhaustion. 

I use mostly nfsv4 mount. 
i have check of that kind of logs in my netapp about storepool but i got no message and no warning too from my nabox 
I use one ip per svm and use round robin too 

Public