We are running MongoDb 3.4.20. Environment is IBM Cloud Private 3.1.2 running on an Ubuntu 18.04 Server. The MongoDB is part of IBM Cloud Automation Manager. We first mounted the PV required by the MongoDB pod on an NFS Share provided by MS Windows Server and received the following errors in the logs:

2019-07-04T08:20:09.367Z E STORAGE  [thread2] WiredTiger error (13) [1562228409:367295][9:0x7f381af0e700], file:WiredTiger.wt, WT_SESSION.checkpoint: /data/db/WiredTiger.turtle.set to /data/db/WiredTiger.turtle: file-rename: rename: Permission denied
2019-07-04T08:20:09.369Z E STORAGE  [thread2] WiredTiger error (0) [1562228409:369459][9:0x7f381af0e700], file:WiredTiger.wt, WT_SESSION.checkpoint: WiredTiger.turtle: encountered an illegal file format or internal value
2019-07-04T08:20:09.369Z E STORAGE  [thread2] WiredTiger error (-31804) [1562228409:369535][9:0x7f381af0e700], file:WiredTiger.wt, WT_SESSION.checkpoint: the process must exit and restart: WT_PANIC: WiredTiger library panic

After restarting the MongoDB pod, it would run for a while and then fail with the same error. After switching to a linux NFS server the problem no longer occurs. I have seen a similar problem reported earlier but which was supposedly fixed in 3.4.14. Because of architectural consideration for the total solution using Windows NFS is preferred by my client. Any suggestions would be welcome.