ec2-consistent-snapshot mongodb - mongod.lock file
I'm trying out ec2-consistent-snapshot with --mongo --freeze-filesystem
options. The snapshot itself works great.
However, after I restore the volume and try to use it with a new instance,
when I launch mongodb I am getting this error:
old lock file: /db/mongodb/mongod.lock. probably means unclean shutdown,
but there are no journal files to recover.
this is likely human error or filesystem corruption.
please make sure that your journal directory is mounted.
and mongo won't launch.
Is it safe to delete the mongod.lock file? Do I need to run a --repair? I
can't find anything specific in the guide or the github repo - but maybe
I'm missing something obvious...
No comments:
Post a Comment