Skip Navigation

How to fix “WARNING:NFS file system mounted with incorrect options” when archivelogs or auto-backups are saved in NFS mount

  • author-thumb
  • B K
  • 10 May 2020

You might have noticed that when we try to store archived logs or RMAN auto-backup files on an NFS mount, we will encounter the below error message in some databases 

WARNING:NFS file system mounted with incorrectoptions(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,soft,noacl,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.249.124.245,mountvers=3,mountport=59649,mountproto=tcp,local_lock=none,addr=10.249.124.245)
WARNING:Expected NFS mount options: rsize>=32768,wsize>=32768,hard,
ARC1 (PID:356486): Unable to create archive log file '/LOG49993_1_993531052.arc'
2020-05-05T01:22:09.256668-04:00 Errors in file /diag/rdbms/orcl1_arc1_356486.trc:
ORA-19504: failed to create file "/LOG49993_1_993531052.arc"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
..
WARNING:NFS file system /mnt mounted with incorrect options(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,soft,noacl,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.249.124.245,mountvers=3,mountport=59649,mountproto=tcp,local_lock=none,addr=10.249.124.245)
WARNING:Expected NFS mount options: rsize>=32768,wsize>=32768,hard,

I noticed this error while taking RMAN backup of a 19c database. It would not take the controlfile auto-backup at the end of the backup, instead it will show this error. (The logs you see here is from the DB alert log, when I tried to store archivelogs in an NFS mount) 

WARNING:NFS file system /mnt mounted with incorrect options(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,soft,noacl,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.249.124.245,mountvers=3,mountport=59649,mountproto=tcp,local_lock=none,addr=10.249.124.245)

Later I noticed the same error in an 18c database, after patching it to April 2020 PSU

The solution to this problem is rather simple, although I am not exactly sure why this works. Just enable the below event in your database. If you already have another events enabled, add this event along with those 

*.event='10298 trace name context forever, level 32'

This solved the problem for me. Hope this helps you too.

Add a comment