|
I cannot reproduce this on newer versions. MongoDB 2.2.1 is very old and no longer updated (or really supported) so we would need to be able to reproduce this on a current stable release in order to address it.
db.fsyncLock()
|
{
|
"info" : "now locked against writes, use db.fsyncUnlock() to unlock",
|
"seeAlso" : "http://dochub.mongodb.org/core/fsynccommand",
|
"ok" : 1
|
}
|
db.fsyncLock()
|
{
|
"info" : "now locked against writes, use db.fsyncUnlock() to unlock",
|
"seeAlso" : "http://dochub.mongodb.org/core/fsynccommand",
|
"ok" : 1
|
}
|
db.currentOp()
|
{
|
"inprog" : [ ],
|
"fsyncLock" : true,
|
"info" : "use db.fsyncUnlock() to terminate the fsync write/snapshot lock"
|
}
|
db.a.findOne()
|
{ "_id" : "ts", "_class" : "foo", "ts" : Timestamp(1411565260, 1) }
|
db.fsyncUnlock()
|
{ "ok" : 1, "info" : "unlock completed" }
|
db.fsyncUnlock()
|
{ "ok" : 1, "info" : "unlock completed" }
|
db.fsyncUnlock()
|
{ "ok" : 0, "errmsg" : "not locked" }
|
NOTE: currentOp has a flag indicating if the server is currently fsyncLocked.
|