Details
-
Bug
-
Resolution: Duplicate
-
Minor - P4
-
None
-
None
-
None
-
None
-
Any
-
ALL
Description
Running db.fsyncLock() causes mongod to become permanently locked and unusable if no databases have been opened. User can't unlock it or re-connect to the mongod. SIG-TERM also is non-functional.
It seemed to quit with SIG-QUIT.
It seems as though when you run `show dbs` it works as expected (databases are opened), but when you don't it breaks.
- Not Working
MongoDB shell version: 2.2.1connecting to: test> db.fsyncLock(){"info" : "now locked against writes, use db.fsyncUnlock() to unlock","seeAlso" : "http://dochub.mongodb.org/core/fsynccommand","ok" : 1}> db.foo.find()# You've just made mongod very unhappy
- Working
MongoDB shell version: 2.2.1connecting to: test> show dbs10gen-hc-2012-8-14 0.203125GB10gen-hc-2012-9-14 0.203125GBadmin 0.203125GBfoo 0.203125GBhub 0.203125GBlocal (empty)mongo-dev 0.203125GBmongo_hadoop 0.453125GBruby-test-db 0.203125GBruby487_development 0.203125GBsomedb 0.203125GBtest 0.203125GBtraining 0.203125GB> db.fsyncLock(){"info" : "now locked against writes, use db.fsyncUnlock() to unlock","seeAlso" : "http://dochub.mongodb.org/core/fsynccommand","ok" : 1}> db.foo.find(){ "_id" : ObjectId("508e9b8b08d6faac46000000"), "foo" : 2 }>
Attachments
Issue Links
- duplicates
-
SERVER-1423 reads often aren't possible while in fsync and lock mode
-
- Closed
-