[SERVER-39937] file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt Created: 03/Mar/19 Updated: 08/Mar/19 Resolved: 08/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.4.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | hexiaojie | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
I am running MongoDB v3.4.6 2019-03-01T15:14:52.797+0800 I CONTROL [main] ***** SERVER RESTARTED ***** , operationProfiling: { mode: "slowOp" }, processManagement: { fork: true, pidFilePath: "/home/mongodb/tmp/shard1.pid" }, replication: { replSetName: "shard1" }, security: { authorization: "enabled ", keyFile: "/home/mongodb/confs/mongod.key" }, setParameter: { enableLocalhostAuthBypass: "false" }, sharding: { clusterRole: "shardsvr" }, storage: { dbPath: "/home/mongodb/datas /shard1", engine: "wiredTiger", journal: { enabled: true }, wiredTiger: { engineConfig: { cacheSizeGB: 2.0 } } }, systemLog: { destination: "file", logAppend: true, logRotate: "reopen", path: "/home/mongodb/logs/shard1.log" } } |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 08/Mar/19 ] |
|
Hello, I see that these are the same files as in Thank you, Danny |
| Comment by hexiaojie [ 08/Mar/19 ] |
|
That's great. It's OK. Can you kindly help me to repair another one(repair-other.rar |
| Comment by Danny Hatcher (Inactive) [ 07/Mar/19 ] |
|
Hello, Unfortunately, I was able to repair the files via an internal script that is not currently available to the public. In order to avoid these problems in the future, we recommend configuring replica sets across multiple servers and taking regular backups of your data. Thank you, Danny |
| Comment by hexiaojie [ 07/Mar/19 ] |
|
Thank you,The problem has been solved,can you share the fix ?
|
| Comment by Danny Hatcher (Inactive) [ 06/Mar/19 ] |
|
Hello, Please extract repair-attempt.tar Thank you, Danny |
| Comment by hexiaojie [ 06/Mar/19 ] |
|
WiredTiger.wt Hello, the members not in the replica set all on the same server,But it happend ,so I want to know how to repair this file, can you share? Thank you,
|
| Comment by Danny Hatcher (Inactive) [ 05/Mar/19 ] |
|
Hello, If you provide the WiredTiger.wt and WiredTiger.turtle files I can attempt a repair. However, having a replica set should avoid the need for this. Were the members in the replica set all on the same server and that server crashed? Thank you, Danny |
| Comment by hexiaojie [ 05/Mar/19 ] |
|
This is correct, but other nodes in my database have the same problem, so I can't sync from a healthy node in the replica set. I want to repair the wiredtig.wt file, but I don't know how to fix this file.So I need some guidance |
| Comment by Danny Hatcher (Inactive) [ 04/Mar/19 ] |
|
Hello, It appears that your database files may have become corrupted. I see that this node is part of a replica set; the best solution would be to perform an initial sync from a healthy node in the replica set. Would this be possible? Thank you, Danny |