-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: WiredTiger
-
None
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Hi,
I got the same issue with this one: SERVER-25285
One different detail...
I was able to start mongo using --repair however it would go down few seconds later when running some queries..
The database crashed when I tried to dump using mongodump.
Then I tried to dump the collections one by one.
That dump worked for all the collections except by one called "user_photos"
It is not a big collections, only 4554 documents.
> db.user_photos.count()
4554
When running mongodump for this specific collection would make the mongo crash with same message on log:
2017-04-23T00:19:33.460-0300 E STORAGE [conn6] WiredTiger error (0) [1492917573:460488][21787:0x7f7449c2d700], file:collection-182-5605041607111941117.wt, WT_CURSOR.next: read checksum error for 8192B block at offset 614400: calculated block checksum of 3087355304 doesn't match expected checksum of 2418908030 2017-04-23T00:19:33.460-0300 E STORAGE [conn6] WiredTiger error (0) [1492917573:460554][21787:0x7f7449c2d700], file:collection-182-5605041607111941117.wt, WT_CURSOR.next: collection-182-5605041607111941117.wt: encountered an illegal file format or internal value 2017-04-23T00:19:33.460-0300 E STORAGE [conn6] WiredTiger error (-31804) [1492917573:460568][21787:0x7f7449c2d700], file:collection-182-5605041607111941117.wt, WT_CURSOR.next: the process must exit and restart: WT_PANIC: WiredTiger library panic 2017-04-23T00:19:33.460-0300 I - [conn6] Fatal Assertion 28558 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 361 2017-04-23T00:19:33.460-0300 I - [conn6] ***aborting after fassert() failure
Can you guys help me fixing?
Production system is down
thank you!