You can find fllow information in mongodb log
Thu Nov 10 23:17:42 [initandlisten] MongoDB starting : pid=19198 port=27017 dbpath=/data/db/ 64-bit host=localhost.localdomain
Thu Nov 10 23:17:42 [initandlisten] db version v2.0.1, pdfile version 4.5
Thu Nov 10 23:17:42 [initandlisten] git version:
3a5cf0e2134a830d38d2d1aae7e88cac31bdd684
Thu Nov 10 23:17:42 [initandlisten] build info: Linux bs-linux64.10gen.cc 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64
BOOST_LIB_VERSION=1_41
Thu Nov 10 23:17:42 [initandlisten] options: { config: "etc/mongo.conf", dbpath:
"/data/db/", fork: "1", journal: "1", logpath:
"/opt/wwh/mongo/logs/mongodb.log", maxConns: 200, port: 27017,
repair: true, repairpath: "/tmp", syncdelay: 30.0 }
**************
old lock file: /data/db/mongod.lock. probably means unclean shutdown,
but there are no journal files to recover.
this is likely human error or filesystem corruption.
found 3 dbs.
see: http://dochub.mongodb.org/core/repair for more information
*************
Start Repair:
Step 1: stop mongod & backup and delete mongodb.log
kill -2 `ps aux |grep mongod |grep -v grep |awk ‘{print $2}’`
rm –f mongodb.log
Step 2: Dlete mongod process lock
rm –f /data/db/mongod.lock
Step 3: Start Reapir mongod
bin/mongod –f etc/mongodb.conf –repair –repairpath /tmp
