WiredTiger error with fallocate while trying to start the server on NFS volume

Ops and Admin
1

Hi,

I am facing below error when I try to start the MongoDB server. This is not a upgraded setup and the dbPath is on a NFS volume. Please can you let me know , how to resolve this? Build version is 4.4.3

{"t":{"$date":"2021-04-07T15:18:37.887+05:30"},"s":"E",  "c":"STORAGE",  "id":22435,   "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":95,"message":"[1617788917:887666][13179:0x7f20dfe68f00], connection: __posix_std_fallocate, 58: **/data/mongodb/journal/WiredTigerTmplog.0000000001: fallocate:: Operation not supported"}}**
{"t":{"$date":"2021-04-07T15:18:37.887+05:30"},"s":"E",  "c":"STORAGE",  "id":22435,   "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":95,"message":"[1617788917:887744][13179:0x7f20dfe68f00], connection: __posix_sys_fallocate, 75: /data/mongodb/journal/WiredTigerTmplog.0000000001: fallocate:: Operation not supported"}}
{"t":{"$date":"2021-04-07T15:19:07.909+05:30"},"s":"E",  "c":"STORAGE",  "id":22435,   "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":2,"message":"[1617788947:909845][13179:0x7f20dfe68f00], txn-recover: __posix_open_file, 808: /data/mongodb/journal/WiredTigerLog.0000000027: handle-open: open: No such file or directory"}}
{"t":{"$date":"2021-04-07T15:19:07.909+05:30"},"s":"E",  "c":"STORAGE",  "id":22435,   "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":2,"message":"[1617788947:909937][13179:0x7f20dfe68f00], txn-recover: __wt_log_scan, 2420: WiredTiger is unable to read the recovery log: No such file or directory"}}
{"t":{"$date":"2021-04-07T15:19:07.909+05:30"},"s":"E",  "c":"STORAGE",  "id":22435,   "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":2,"message":"[1617788947:909958][13179:0x7f20dfe68f00], txn-recover: __wt_log_scan, 2423: This may be due to the log files being encrypted, being from an older version or due to corruption on disk: No such file or directory"}}
{"t":{"$date":"2021-04-07T15:19:07.909+05:30"},"s":"E",  "c":"STORAGE",  "id":22435,   "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":2,"message":"[1617788947:909968]**[13179:0x7f20dfe68f00], txn-recover: __wt_log_scan, 2426: You should confirm that you have opened the database with the correct options including all encryption and compression options: No such file or directory"}}**
2

Hi @Akshaya_Srinivasan,

Please provide some more background on this environment:

  • Have you checked the permissions for your dbPath against your the user your mongod process is running as? The No such file or directory errors suggest a file path or permission problem.

  • You mention this was not an upgraded setup – was MongoDB running successfully before? If so, what has changed recently?

  • What options are you using for your NFS mount point?

Regards,
Stennie

3

hi @Stennie_X

Thanks for your reply. Identified the issue. Due to locking and unlocking the server during backup, it led to journal file roll over which caused this issue. Fixed it.

Whereas this error , looks like a soft error. Server startup is not affected by this.
{“t”:{"$date":“2021-04-07T15:18:37.887+05:30”},“s”:“E”, “c”:“STORAGE”, “id”:22435, “ctx”:“initandlisten”,“msg”:“WiredTiger error”,“attr”:{“error”:95,“message”:"[1617788917:887666][13179:0x7f20dfe68f00], connection: __posix_std_fallocate, 58: /data/mongodb/journal/WiredTigerTmplog.0000000001: fallocate:: Operation not supported"}}

4

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.