- 
    Type:
Question
 - 
    Resolution: Incomplete
 - 
    Priority:
Major - P3
 - 
    None
 - 
    Affects Version/s: 2.0.4
 - 
    Component/s: Replication
 - 
    Environment:Linux Debian Squeeze
 
- 
        None
 
- 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 
I badly need to access the replication op log after a serious data corruption that occurred while trying to copy databases on the same server.
I have the following 5 local files in the current db path.
64M		local.0
128M		local.1
2.0G		local.2
2.0G		local.3
2.0G		local.4
When I acces the "local" db via the mongo shell and the according "oplog.rs" collection, I only see 3 entries. Prior to the crash, I had upwards of 600,000 entries and so am hoping they have been orphaned in the local.1 - local.4 files.
Is there any that I can verify whether these rows still exist and, if so, how might I access them?
Thanks for any help you can provide.
-Robert Poskevich