[SERVER-22207] Repair operation error - " Cannot allocate memory but file doesn't exist anymore, so ignoring" Created: 16/Jan/16  Updated: 05/Mar/16  Resolved: 05/Mar/16

Status: Closed
Project: Core Server
Component/s: Admin, Storage
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Dharshan Rangegowda Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Hi folks,

I am running a repair operation and it appears to get stuck with the following error

2016-01-15T01:39:57.583+0000 [DataFileSync] flushing mmaps took 361607ms  for 657 files
2016-01-15T01:39:57.638+0000 [DataFileSync] msync failed with: errno:12 Cannot allocate memory but file doesn't exist anymore, so ignoring
2016-01-15T01:39:57.638+0000 [DataFileSync] msync failed with: errno:12 Cannot allocate memory but file doesn't exist anymore, so ignoring
2016-01-15T01:39:57.638+0000 [DataFileSync] msync failed with: errno:12 Cannot allocate memory but file doesn't exist anymore, so ignoring
2016-01-15T01:39:57.638+0000 [DataFileSync] msync failed with: errno:12 Cannot allocate memory but file doesn't exist anymore, so ignoring
2016-01-15T01:39:57.638+0000 [DataFileSync] msync failed with: errno:12 Cannot allocate memory but file doesn't exist anymore, so ignoring

The process was still running - but I terminated it after several hours. I also see a lot of the following messages in the log

2016-01-15T01:36:49.736+0000 [initandlisten] warning Listener::getElapsedTimeMillis returning 0ms

The process was started with the following command

mongod --port 37017 --dbpath /mongodb_data --repair --repairpath /mongodb_data/repair --logpath /mongodb_data/repair.log

Mongo version is 2.6.x



 Comments   
Comment by Ramon Fernandez Marina [ 05/Mar/16 ]

Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Regards,
Ramón.

Generated at Thu Feb 08 03:59:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.