[SERVER-19126] error: { "$err" : "assertion src/mongo/db/storage/extent_manager.cpp:109" } Created: 25/Jun/15  Updated: 10/Aug/15  Resolved: 10/Aug/15

Status: Closed
Project: Core Server
Component/s: Stability
Affects Version/s: 2.6.10
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Kishor Panpatte [X] Assignee: Sam Kleinman (Inactive)
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Hi,
We are using mongodb version 2.6.10 we are getting fallowing error ,

we are not able to get backup and and even read the some collection from db.

please guide how to retrieve date from such collection also cause and solution of these problem

Error:

rdp_mdb.tinyurlmd Assertion failure n >= 0 && n < static_cast<int>(_files.size()) src\mongo\db\storage\extent_manager.cpp 109
mongod.exe    ...\src\mongo\util\log.cpp(127)                                       mongo::logContext+0xa7
mongod.exe    ...\src\mongo\util\assert_util.cpp(114)                               mongo::verifyFailed+0x166
mongod.exe    ...\src\mongo\db\storage\extent_manager.cpp(110)                      mongo::ExtentManager::_getOpenFile+0xc4
mongod.exe    ...\src\mongo\db\storage\extent_manager.cpp(227)                      mongo::ExtentManager::getExtent+0x25
mongod.exe    ...\src\mongo\db\catalog\collection.cpp(401)                          mongo::Collection::storageSize+0x87
mongod.exe    ...\src\mongo\db\dbcommands.cpp(1075)                                 mongo::CollectionStats::run+0x4bd
mongod.exe    ...\src\mongo\db\dbcommands.cpp(1388)                                 mongo::_execCommand+0x66
mongod.exe    ...\src\mongo\db\dbcommands.cpp(1620)                                 mongo::Command::execCommand+0xb9d
mongod.exe    ...\src\mongo\db\dbcommands.cpp(1725)                                 mongo::_runCommands+0x40f
mongod.exe    ...\src\mongo\db\query\new_find.cpp(125)                              mongo::runCommands+0x4c
mongod.exe    ...\src\mongo\db\query\new_find.cpp(442)                              mongo::newRunQuery+0x32c
mongod.exe    ...\src\mongo\db\instance.cpp(269)                                    mongo::receivedQuery+0x311
mongod.exe    ...\src\mongo\db\instance.cpp(439)                                    mongo::assembleResponse+0x32f
mongod.exe    ...\src\mongo\db\db.cpp(204)                                          mongo::MyMessageHandler::process+0x11f
mongod.exe    ...\src\mongo\util\net\message_server_port.cpp(210)                   mongo::PortMessageServer::handleIncomingMsg+0x4fc
mongod.exe    ...\src\third_party\boost\boost\thread\detail\thread.hpp(62)          boost::detail::thread_data<boost::_bi::bind_t<void *,void * (__cdecl*)(void *),boost::_bi::list1<boost::_bi::value<mongo::PortMessageServer::HandleIncomingMsgParam *> > > >::run+0x9
mongod.exe    ...\src\third_party\boost\libs\thread\src\win32\thread.cpp(16707566)  boost::`anonymous namespace'::thread_start_function+0x7b
mongod.exe    f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c(314)                _callthreadstartex+0x1b
mongod.exe    f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c(292)                _threadstartex+0x64
kernel32.dll                                                                        BaseThreadInitThunk+0x12



 Comments   
Comment by Ramon Fernandez Marina [ 03/Aug/15 ]

Kishorp, we haven't heard back from you for some time. If this is still an issue for you, can you please post the information requested by Sam above? This type of error messages signal data corruption, typically caused by a flaky storage layer, networking errors, or interference with files in dbpath (e.g.: improper use of snapshots). Sam's questions should help us get to the source of the corruption.

Thanks,
Ramón.

Comment by Sam Kleinman (Inactive) [ 02/Jul/15 ]

Hello,

To help understand this issue a bit better, I'd like to ask you a few questions about your deployment and this instance.

  1. Is this instance part of a replica set? If so what role was the member when you encountered this issue?
  2. Does this instance use journaling?
  3. Does this instance use the directoryPerDb setting?
  4. What kind of underlying storage mechanism are you using? Are the storage devices attached locally or over the network? Are the disks SSDs or HDDs? What kind of RAID and/or volume management system are you using?
  5. Have you manipulated (coppied or moved) the underling database files?
  6. Have you ever restored this instance from backups?
  7. What method do you use to create back ups?

Thanks for this report and sorry again for the inconvenience.

Regards,
sam

Comment by Kishor Panpatte [X] [ 25/Jun/15 ]

Hi Ramon,

only below log are display from mongodb while we are applying find query on collection.

==logs==

2015-06-25T19:19:31.683+0530 [conn2] uh oh: 1
2015-06-25T19:19:31.683+0530 [conn2] rdp_mdb.tinyurlmd Assertion failure n >= 0 && n < static_cast<int>(_files.size()) src\mongo\db\storage\extent_manager.cpp 109
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\util\log.cpp(127) mongo::logContext+0xa7
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\util\assert_util.cpp(114) mongo::verifyFailed+0x166
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\db\storage\extent_manager.cpp(110) mongo::ExtentManager::_getOpenFile+0xc4
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\db\storage\extent_manager.cpp(227) mongo::ExtentManager::getExtent+0x25
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\db\catalog\collection.cpp(401) mongo::Collection::storageSize+0x87
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\db\dbcommands.cpp(1075) mongo::CollectionStats::run+0x4bd
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\db\dbcommands.cpp(1388) mongo::_execCommand+0x66
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\db\dbcommands.cpp(1620) mongo::Command::execCommand+0xb9d
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\db\dbcommands.cpp(1725) mongo::_runCommands+0x40f
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\db\query\new_find.cpp(125) mongo::runCommands+0x4c
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\db\query\new_find.cpp(442) mongo::newRunQuery+0x32c
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\db\instance.cpp(269) mongo::receivedQuery+0x311
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\db\instance.cpp(439) mongo::assembleResponse+0x32f
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\db\db.cpp(204) mongo::MyMessageHandler::process+0x11f
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\mongo\util\net\message_server_port.cpp(210) mongo::PortMessageServer::handleIncomingMsg+0x4fc
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\third_party\boost\boost\thread\detail\thread.hpp(62) boost::detail::thread_data<boost::bi::bind_t<void ,void * (_cdecl)(void *),boost::_bi::list1<boost::_bi::value<mongo::PortMessageServer::HandleIncomingMsgParam *> > > >::run+0x9
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe ...\src\third_party\boost\libs\thread\src\win32\thread.cpp(16707566) boost::`anonymous namespace'::thread_start_function+0x7b
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c(314) _callthreadstartex+0x1b
2015-06-25T19:19:32.525+0530 [conn2] mongod.exe f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c(292) _threadstartex+0x64
2015-06-25T19:19:32.525+0530 [conn2] kernel32.dll BaseThreadInitThunk+0x12
2015-06-25T19:19:32.525+0530 [conn2] rdp_mdb.tinyurlmd
2015-06-25T19:19:32.525+0530 [conn2] command rdp_mdb.$cmd command: collStats

{ collStats: "tinyurlmd", scale: 1 }

ntoreturn:1 keyUpdates:0 numYields:0 locks(micros) r:849254 reslen:187 849ms
2015-06-25T19:19:56.431+0530 [initandlisten] connection accepted from 127.0.0.1:49884 #6 (6 connections now open)

Comment by Ramon Fernandez Marina [ 25/Jun/15 ]

Kishorp, can you please upload more detailed logs from this server? There are lines before the log snippet above that may contain useful information for diagnosing this issue.

Thanks,
Ramón.

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