-
Type: Question
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
[root@ZhiJiao-B mongo]# mongod --dbpath /DATA/gttt/mongo/db --repair
2019-01-16T22:10:03.484+0800 I CONTROL [initandlisten] MongoDB starting : pid=29607 port=27017 dbpath=/DATA/gttt/mongo/db 64-bit host=ZhiJiao-B
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] db version v3.2.10
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] git version: 79d9b3ab5ce20f51c272b4411202710a082d0317
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] allocator: tcmalloc
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] modules: none
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] build environment:
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] distarch: x86_64
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] target_arch: x86_64
2019-01-16T22:10:03.485+0800 I CONTROL [initandlisten] options: { repair: true, storage:
}
2019-01-16T22:10:03.499+0800 I - [initandlisten] Detected data files in /DATA/gttt/mongo/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2019-01-16T22:10:03.499+0800 I STORAGE [initandlisten] Detected WT journal files. Running recovery from last checkpoint.
2019-01-16T22:10:03.499+0800 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=18G,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2019-01-16T22:10:03.509+0800 E STORAGE [initandlisten] WiredTiger (-31802) [1547647803:509217][29607:0x7f20a0ab6cc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2019-01-16T22:10:03.509+0800 E STORAGE [initandlisten] WiredTiger (0) [1547647803:509278][29607:0x7f20a0ab6cc0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
2019-01-16T22:10:03.509+0800 E STORAGE [initandlisten] WiredTiger (0) [1547647803:509296][29607:0x7f20a0ab6cc0], file:WiredTiger.wt, connection: This may be due to the database files being encrypted, being from an older version or due to corruption on disk
2019-01-16T22:10:03.509+0800 E STORAGE [initandlisten] WiredTiger (0) [1547647803:509313][29607:0x7f20a0ab6cc0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
2019-01-16T22:10:03.509+0800 I - [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error
2019-01-16T22:10:03.509+0800 I STORAGE [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2019-01-16T22:10:03.509+0800 I CONTROL [initandlisten] dbexit: rc: 100
- is duplicated by
-
SERVER-39028 WiredTiger (-31802) [1547647803:509217][29607:0x7f20a0ab6cc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
- Closed
- is related to
-
WT-4554 Enhance WT salvage to handle the case of corrupted WiredTiger.turtle
- Closed